Skip to content

Conversation

Neeraj8418
Copy link

This PR introduces a conditional filter to include .ins and .addrsize PXE artifacts only when the target CPU architecture is s390x during ABI-based Day-2 node image creation using oc adm node-image create.

Changes:

Updated the create.go logic to check for s390x CPU architecture before including:
*.ins
*.addrsize

Testing
Tested by:
Running the oc adm node-image create for s390x and verified only s390x-relevant PXE files are generated.
Ensured no regression on other platforms — .ins and .addrsize are excluded when architecture is not s390x.

@openshift-ci openshift-ci bot requested review from pawanpinjarkar and zaneb April 15, 2025 04:55
@Neeraj8418 Neeraj8418 changed the title Add s390x-specific PXE artifacts filter for .ins and .addrsize [OCPBUGS-52164]: Add the generation of initrd.addrsize and generic.ins file for ABI Day2 Artifacts. Apr 15, 2025
@Neeraj8418 Neeraj8418 requested a review from zaneb April 15, 2025 12:25
@Neeraj8418
Copy link
Author

/retest

@@ -381,7 +381,8 @@ func (o *CreateOptions) copyArtifactsFromNodeJoinerPod() error {
}
if o.GeneratePXEFiles {
rsyncOptions.Source.Path = "/assets/boot-artifacts/"
rsyncOptions.RsyncInclude = []string{"*.img", "*.*vmlinuz", "*.ipxe"}
rsyncOptions.RsyncInclude = nil
rsyncOptions.RsyncExclude = []string{".*"}
Copy link
Contributor

@andfasano andfasano Apr 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also commented in the other thread, but this seems to gather too much stuff (as previously fixed in #1931), did you maybe verify it? Thanks cc @Neeraj8418

Copy link
Author

@Neeraj8418 Neeraj8418 Apr 16, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @andfasano , I just verified for s390x and that only copied the required images. No additional stuff were added.

[root@m42lp51 day2]# ll
total 1079148
-rw-r--r--. 1 root root        149 Apr 15 14:23 node.s390x-generic.ins
-rw-r--r--. 1 root root         16 Apr 15 14:23 node.s390x-initrd.addrsize
-rw-r--r--. 1 root root   64771460 Apr 15 14:23 node.s390x-initrd.img
-rw-r--r--. 1 root root    9253349 Apr 15 14:23 node.s390x-kernel.img
-rw-r--r--. 1 root root 1031003648 Apr 15 14:23 node.s390x-rootfs.img
-rw-r--r--. 1 root root        712 Apr 14 16:32 nodes-config.yaml

Does this looks fine or shall i revert it back to previous changes?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd feel more comfortable into having an explicit list of files (extensions) to be included, rather than an exclusion list that may catch in future unwanted files.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok sure @andfasano . I have forced pushed the changed to first commit now. This branch has an explicit list of files to be included.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Personally I'd feel more comfortable knowing that we can change the installer in future, but OCPBUGS-45311 doesn't specify what extra files were previously being added so it is hard to evaluate, and we have already messed Neeraj around enough, so I LGTMd.

@Neeraj8418
Copy link
Author

/retest

1 similar comment
@Neeraj8418
Copy link
Author

/retest

@Neeraj8418 Neeraj8418 requested a review from andfasano April 16, 2025 10:39
@Neeraj8418
Copy link
Author

/retest

@andfasano
Copy link
Contributor

/approve

@Neeraj8418
Copy link
Author

/retest

3 similar comments
@Neeraj8418
Copy link
Author

/retest

@Neeraj8418
Copy link
Author

/retest

@Neeraj8418
Copy link
Author

/retest

@Neeraj8418
Copy link
Author

/jira-refresh

@Neeraj8418
Copy link
Author

/retest

2 similar comments
@Neeraj8418
Copy link
Author

/retest

@Neeraj8418
Copy link
Author

/retest

@zaneb
Copy link
Member

zaneb commented Apr 22, 2025

/retitle OCPBUGS-52164: Add the generation of initrd.addrsize and generic.ins file for ABI Day2 Artifacts
/lgtm

@openshift-ci openshift-ci bot changed the title [OCPBUGS-52164]: Add the generation of initrd.addrsize and generic.ins file for ABI Day2 Artifacts. OCPBUGS-52164: Add the generation of initrd.addrsize and generic.ins file for ABI Day2 Artifacts Apr 22, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Apr 22, 2025
@openshift-ci-robot
Copy link

@Neeraj8418: This pull request references Jira Issue OCPBUGS-52164, 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.19.0) matches configured target version for branch (4.19.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.

In response to this:

This PR introduces a conditional filter to include .ins and .addrsize PXE artifacts only when the target CPU architecture is s390x during ABI-based Day-2 node image creation using oc adm node-image create.

Changes:

Updated the create.go logic to check for s390x CPU architecture before including:
*.ins
*.addrsize

Testing
Tested by:
Running the oc adm node-image create for s390x and verified only s390x-relevant PXE files are generated.
Ensured no regression on other platforms — .ins and .addrsize are excluded when architecture is not s390x.

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-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Apr 22, 2025
@openshift-ci openshift-ci bot requested a review from mhanss April 22, 2025 21:52
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 22, 2025
Copy link
Contributor

openshift-ci bot commented Apr 22, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andfasano, Neeraj8418, zaneb

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

The pull request process is described here

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 Apr 22, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD beeaf09 and 2 for PR HEAD 3cce51a in total

@Neeraj8418
Copy link
Author

/retest

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD c651008 and 1 for PR HEAD 3cce51a in total

@Neeraj8418
Copy link
Author

/pj-rehearse ack

@Neeraj8418
Copy link
Author

/retest-required

1 similar comment
@Neeraj8418
Copy link
Author

/retest-required

@Neeraj8418
Copy link
Author

/retest

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD c651008 and 2 for PR HEAD 3cce51a in total

Copy link
Contributor

openshift-ci bot commented Apr 24, 2025

@Neeraj8418: all tests passed!

Full PR test history. Your PR dashboard.

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 306c7b3 into openshift:master Apr 24, 2025
15 checks passed
@openshift-ci-robot
Copy link

@Neeraj8418: Jira Issue OCPBUGS-52164: All pull requests linked via external trackers have merged:

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

In response to this:

This PR introduces a conditional filter to include .ins and .addrsize PXE artifacts only when the target CPU architecture is s390x during ABI-based Day-2 node image creation using oc adm node-image create.

Changes:

Updated the create.go logic to check for s390x CPU architecture before including:
*.ins
*.addrsize

Testing
Tested by:
Running the oc adm node-image create for s390x and verified only s390x-relevant PXE files are generated.
Ensured no regression on other platforms — .ins and .addrsize are excluded when architecture is not s390x.

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-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-cli
This PR has been included in build openshift-enterprise-cli-container-v4.19.0-202504240553.p0.g306c7b3.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-tools
This PR has been included in build ose-tools-container-v4.19.0-202504240553.p0.g306c7b3.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-deployer
This PR has been included in build openshift-enterprise-deployer-container-v4.19.0-202504240553.p0.g306c7b3.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-cli-artifacts
This PR has been included in build ose-cli-artifacts-container-v4.19.0-202504240553.p0.g306c7b3.assembly.stream.el9.
All builds following this will include this PR.

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.19.0-0.nightly-2025-04-29-095709

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. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants