Skip to content

Conversation

@barbacbd
Copy link
Contributor

** Update the data directory for the motd file to include the node-image-ull service.

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 25, 2025
@openshift-ci-robot
Copy link
Contributor

@barbacbd: This pull request references Jira Issue OCPBUGS-57126, which is invalid:

  • expected the bug to target the "4.21.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

Details

In response to this:

** Update the data directory for the motd file to include the node-image-ull service.

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.

@barbacbd
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 25, 2025
@openshift-ci-robot
Copy link
Contributor

@barbacbd: This pull request references Jira Issue OCPBUGS-57126, 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.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
Details

In response to this:

/jira refresh

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.

@barbacbd
Copy link
Contributor Author

output

Sep 25 18:39:15 redacted
Sep 25 18:39:15 <>: Fetching redacted
Sep 25 18:39:16 <>: layers already present: 16; layers needed: 37 (1.3 GB)
Sep 25 18:39:16 <>[2210]: layers already present: 16; layers needed: 37 (1.3 GB)
Sep 25 18:40:12 redacted
Sep 25 18:40:14 <>: Checking out node image content
Sep 25 18:40:15 <>: Finished Node Image Pull.
Sep 25 18:40:16 <>: node-image-pull.service: Deactivated successfully.
Sep 25 18:40:16 <>: Stopped Node Image Pull.
Sep 25 18:40:16 <>: node-image-pull.service: Consumed 1min 18.151s CPU time.

…heir logs in /etc/motd

** Update the data directory for the motd file to include the node-image-ull service.
Copy link
Member

@tthvo tthvo left a comment

Choose a reason for hiding this comment

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

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 25, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tthvo

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 Sep 25, 2025
@barbacbd
Copy link
Contributor Author

/retest-required

1 similar comment
@barbacbd
Copy link
Contributor Author

/retest-required

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 17, 2025

@barbacbd: 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/e2e-vsphere-static-ovn 5d9f38c link false /test e2e-vsphere-static-ovn
ci/prow/e2e-azure-ovn-resourcegroup 5d9f38c link false /test e2e-azure-ovn-resourcegroup
ci/prow/e2e-vsphere-ovn-multi-network 5d9f38c link false /test e2e-vsphere-ovn-multi-network
ci/prow/e2e-vsphere-externallb-ovn 5d9f38c link false /test e2e-vsphere-externallb-ovn
ci/prow/okd-scos-e2e-aws-ovn 5d9f38c link false /test okd-scos-e2e-aws-ovn

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.

@barbacbd
Copy link
Contributor Author

/retest-required

@jhixson74
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 24, 2025
@gpei
Copy link
Contributor

gpei commented Oct 25, 2025

/verified by @gpei

With this PR, after logging into the bootstrap node, the system message now includes a mention of node-image-pull.service, as follows:

This is the bootstrap node; it will be destroyed when the master is fully up.

The primary services are release-image.service followed by bootkube.service and node-image-pull.service. To watch their status, run e.g.

  journalctl -b -f -u release-image.service -u bootkube.service -u node-image-pull.service

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 25, 2025
@openshift-ci-robot
Copy link
Contributor

@gpei: This PR has been marked as verified by @gpei.

Details

In response to this:

/verified by @gpei

With this PR, after logging into the bootstrap node, the system message now includes a mention of node-image-pull.service, as follows:

This is the bootstrap node; it will be destroyed when the master is fully up.

The primary services are release-image.service followed by bootkube.service and node-image-pull.service. To watch their status, run e.g.

 journalctl -b -f -u release-image.service -u bootkube.service -u node-image-pull.service

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-merge-bot openshift-merge-bot bot merged commit d7dc751 into openshift:main Oct 25, 2025
14 of 19 checks passed
@openshift-ci-robot
Copy link
Contributor

@barbacbd: Jira Issue Verification Checks: Jira Issue OCPBUGS-57126
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-57126 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

** Update the data directory for the motd file to include the node-image-ull service.

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-merge-robot
Copy link
Contributor

Fix included in accepted release 4.21.0-0.nightly-2025-10-26-145358

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/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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants