[release-4.14] OCPBUGS-47265: fixing CVE-2024-45338

[yanhua121]

[release-4.14] OCPBUGS-47265: fixing CVE-2024-45338

[openshift-ci-robot]

@yanhua121: This pull request references Jira Issue OCPBUGS-47265, which is invalid:

• expected dependent Jira Issue OCPBUGS-47264 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

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.

In response to this:

[release-4.14] OCPBUGS-47265: fixing CVE-2024-45338

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.

[damdo]

/approve
/lgtm

[yanhua121]

/test e2e-nutanix

[JoelSpeed]

/approve
/lgtm
/label backport-risk-assessed

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: damdo, JoelSpeed

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:

• OWNERS [JoelSpeed]

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

[yanhua121]

/test e2e-nutanix-operator

[yanhua121]

/test e2e-nutanix

[yanhua121]

/retest

[sunzhaohua2]

@huali9 this pr can be pre-merge test, then add cherry-pick-approved label

[huali9]

@huali9 this pr can be pre-merge test, then add cherry-pick-approved label

Yes, we can. But even if I do that, this PR will not be merged because the dependent has not been verified, so I'd like to do the dependent bugs first, 4.18->4.17->4.16..., the earliest bug that is dependent here is 4.18 one, let me do pre-merge test for the 4.18 one first. What do you think?

[sunzhaohua2]

let me do pre-merge test for the 4.18 one first. What do you think?

sure, thank you!

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[damdo]

/remove-lifecycle stale

[damdo]

/retest

[damdo]

/retest

[openshift-ci]

@yanhua121: The following test 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-nutanix-operator	4e8d8f5	link	false	/test e2e-nutanix-operator

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.