Skip to content

[WIP] AGENT-1522: bump InternalReleaseImage to v1 (followup) - #733

Closed
andfasano wants to merge 1 commit into
openshift:masterfrom
andfasano:iri-two-manifests
Closed

[WIP] AGENT-1522: bump InternalReleaseImage to v1 (followup)#733
andfasano wants to merge 1 commit into
openshift:masterfrom
andfasano:iri-two-manifests

Conversation

@andfasano

Copy link
Copy Markdown
Contributor

This is a tentative followup of #719. IRI manifests with version v1alpha1 is also pushed (to make happy MCO bootstrap processes)

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 6, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 6, 2026

Copy link
Copy Markdown

@andfasano: This pull request references AGENT-1522 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

This is a tentative followup of #719. IRI manifests with version v1alpha1 is also pushed (to make happy MCO bootstrap processes)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@andfasano

Copy link
Copy Markdown
Contributor Author

/test ?

@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 6, 2026
@openshift-ci

openshift-ci Bot commented Jul 6, 2026

Copy link
Copy Markdown

@andfasano: The following commands are available to trigger required jobs:

/test e2e-compact-ipv4-static
/test images
/test lint
/test unit-test

The following commands are available to trigger optional jobs:

/test e2e-agent-compact-ipv4-iso-no-registry
/test e2e-sno-dualstack-dhcp

Use /test all to run all jobs.

Details

In response to this:

/test ?

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-ci
openshift-ci Bot requested review from pawanpinjarkar and rwsu July 6, 2026 14:23
@openshift-ci

openshift-ci Bot commented Jul 6, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andfasano

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 6, 2026
@openshift-ci

openshift-ci Bot commented Jul 6, 2026

Copy link
Copy Markdown

@andfasano: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/unit-test bff412e link true /test unit-test
ci/prow/e2e-agent-compact-ipv4-iso-no-registry bff412e link false /test e2e-agent-compact-ipv4-iso-no-registry

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@andfasano

Copy link
Copy Markdown
Contributor Author

This approach does not work, since the IRI singleton CEL validation does not allow for a different name. Using the cluster name anyway does not work as well, since the CVOIgnore check is applied at the bootstrap.

@andfasano andfasano closed this Jul 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants