OCPBUGS-64929: coreos-installer iso kargs show broken on OVE Agent ISO

[pawanpinjarkar]

Vendor latest assisted-image-service commit 503834119b3e. This fixes broken iso kargs show results.

coreos-installer iso kargs show agent-ove.x86_64.iso
rw  coreos.liveiso=rhcos-9.6.20251023-0 ignition.firstboot ignition.platform.id=metal

[openshift-ci-robot]

@pawanpinjarkar: This pull request references Jira Issue OCPBUGS-64929, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.22.0) matches configured target version for branch (4.22.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @mhanss

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Vendor latest assisted-image-service commit 503834119b3e

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.

[danielerez]

/retest

[openshift-ci-robot]

@pawanpinjarkar: This pull request references Jira Issue OCPBUGS-64929, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.22.0) matches configured target version for branch (4.22.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @mhanss

Details

In response to this:

Vendor latest assisted-image-service commit 503834119b3e. This fixes broken iso kargs show results.

coreos-installer iso kargs show agent-ove.x86_64.iso
rw  coreos.liveiso=rhcos-9.6.20251023-0 ignition.firstboot ignition.platform.id=metal

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.

[pawanpinjarkar]

/cherrypick release-4.21, release-4.20

[openshift-cherrypick-robot]

@pawanpinjarkar: once the present PR merges, I will cherry-pick it on top of release-4.21, in a new PR and assign it to you.

Details

In response to this:

/cherrypick release-4.21, release-4.20

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.

[pawanpinjarkar]

/cc @zaneb @danielerez

[openshift-ci]

@pawanpinjarkar: all tests passed!

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.

[danielerez]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danielerez, pawanpinjarkar

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:

• OWNERS [danielerez]

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

[openshift-ci-robot]

@pawanpinjarkar: Jira Issue OCPBUGS-64929: All pull requests linked via external trackers have merged:

• openshift/assisted-image-service#620
• openshift/appliance#656

Jira Issue OCPBUGS-64929 has been moved to the MODIFIED state.

Details

In response to this:

Vendor latest assisted-image-service commit 503834119b3e. This fixes broken iso kargs show results.

coreos-installer iso kargs show agent-ove.x86_64.iso
rw  coreos.liveiso=rhcos-9.6.20251023-0 ignition.firstboot ignition.platform.id=metal

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.

[openshift-cherrypick-robot]

@pawanpinjarkar: cannot checkout release-4.21,: error checking out "release-4.21,": exit status 1 error: pathspec 'release-4.21,' did not match any file(s) known to git

Details

In response to this:

/cherrypick release-4.21, release-4.20

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.

[pawanpinjarkar]

/cherrypick release-4.21

[openshift-cherrypick-robot]

@pawanpinjarkar: #656 failed to apply on top of branch "release-4.21":

Applying: OCPBUGS-64929: coreos-installer iso kargs show broken on OVE Agent ISO Vendor latest assisted-image-service commit 503834119b3e
Using index info to reconstruct a base tree...
M	go.mod
M	go.sum
Falling back to patching base and 3-way merge...
Auto-merging go.sum
CONFLICT (content): Merge conflict in go.sum
Auto-merging go.mod
CONFLICT (content): Merge conflict in go.mod
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 OCPBUGS-64929: coreos-installer iso kargs show broken on OVE Agent ISO Vendor latest assisted-image-service commit 503834119b3e

Details

In response to this:

/cherrypick release-4.21

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.

[zaneb]

Looks like we dropped the change from #580, but I'm unclear on the significance of that.

[pawanpinjarkar]

I discussed with @danielerez. As suggested, its not crucial, the konflux bot should handle it again.