Skip to content

[release-4.21] OCPBUGS-100051: Bump ironic-python-agent pinned commit for CVE-2026-66138 - #296

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.21from
mariocr73:OCPBUGS-100051-421
Aug 20, 2026
Merged

[release-4.21] OCPBUGS-100051: Bump ironic-python-agent pinned commit for CVE-2026-66138#296
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.21from
mariocr73:OCPBUGS-100051-421

Conversation

@mariocr73

Copy link
Copy Markdown

Update the pinned ironic-python-agent commit from e624ef77 to 295c9d27, which cherry-picks upstream security fix d4926bf9 (NTP command injection in sync_clock(), CVE-2026-66138) onto the OCP 4.21 branch of the openshift/openstack-ironic-python-agent fork.

Related: OCPBUGS-100051

@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. 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 Jul 29, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@mariocr73: This pull request references Jira Issue OCPBUGS-100051, which is invalid:

  • expected dependent Jira Issue OCPBUGS-99897 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New instead
  • expected dependent Jira Issue OCPBUGS-99897 to target a version in 4.22.0, but it targets "4.22.z" instead

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 pinned ironic-python-agent commit from e624ef77 to 295c9d27, which cherry-picks upstream security fix d4926bf9 (NTP command injection in sync_clock(), CVE-2026-66138) onto the OCP 4.21 branch of the openshift/openstack-ironic-python-agent fork.

Related: OCPBUGS-100051

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.

@coderabbitai

coderabbitai Bot commented Jul 29, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 04c279a9-7f83-4e56-b550-7eb0c5d4e0f4

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@openshift-ci
openshift-ci Bot requested review from dtantsur and elfosardo July 29, 2026 15:23
@mariocr73

Copy link
Copy Markdown
Author

⚠️ This PR depends on openshift/openstack-ironic-python-agent#195 merging first.

The pinned commit 295c9d27 only exists in that (not-yet-merged) PR's branch, which is why ci/prow/check-requirements will fail until it merges — it validates the pinned SHA against the upstream repo. Please hold merging this PR until then.

@mariocr73

Copy link
Copy Markdown
Author

/retest-required

Update the pinned ironic-python-agent commit from 9ab35b82 to 10b10f29
(release-4.21 tip), which includes upstream security fix d4926bf9 (NTP
command injection in sync_clock(), CVE-2026-66138) cherry-picked as
295c9d27 onto the OCP 4.21 branch of the
openshift/openstack-ironic-python-agent fork, merged alongside the
unrelated fix from PR openshift/openstack-ironic-python-agent#189.
Related: OCPBUGS-100051
@mariocr73

Copy link
Copy Markdown
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 Aug 19, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@mariocr73: This pull request references Jira Issue OCPBUGS-100051, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.z) matches configured target version for branch (4.21.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-99897 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-99897 targets the "4.22.z" version, which is one of the valid target versions: 4.22.0
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (ocp-sustaining-admins@redhat.com), skipping review request.

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.

@mariocr73

Copy link
Copy Markdown
Author

/retest-required

@mariocr73

Copy link
Copy Markdown
Author

/retest

@mariocr73

Copy link
Copy Markdown
Author

/test e2e-metal-ipi-ovn-ipv4
/test e2e-metal-ipi-ovn-ipv6
/test e2e-metal-ipi-serial-ipv4
/test e2e-metal-ipi-virtualmedia

@openshift-ci

openshift-ci Bot commented Aug 19, 2026

Copy link
Copy Markdown

@mariocr73: 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.

@mariocr73

Copy link
Copy Markdown
Author

/verified by CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Aug 19, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@mariocr73: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

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.

@elfosardo

Copy link
Copy Markdown

/approve

@elfosardo

Copy link
Copy Markdown

/label backport-risk-assessed

@openshift-ci openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Aug 20, 2026
@openshift-ci

openshift-ci Bot commented Aug 20, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: elfosardo, mariocr73

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 Aug 20, 2026
@hroyrh

hroyrh commented Aug 20, 2026

Copy link
Copy Markdown

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 20, 2026
@openshift-merge-bot

Copy link
Copy Markdown

Tests from second stage were triggered manually. Pipeline can be controlled only manually, until HEAD changes. Use command to trigger second stage.

@openshift-merge-bot
openshift-merge-bot Bot merged commit 156ef6b into openshift:release-4.21 Aug 20, 2026
9 checks passed
@openshift-ci-robot

Copy link
Copy Markdown

@mariocr73: Jira Issue OCPBUGS-100051: All pull requests linked via external trackers have merged:

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

Details

In response to this:

Update the pinned ironic-python-agent commit from e624ef77 to 295c9d27, which cherry-picks upstream security fix d4926bf9 (NTP command injection in sync_clock(), CVE-2026-66138) onto the OCP 4.21 branch of the openshift/openstack-ironic-python-agent fork.

Related: OCPBUGS-100051

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.

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/severity-important Referenced Jira bug's severity is important 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants