Skip to content

Comments

[release-4.18] ART-13476: stop installing rpms that are already in the base image#47

Open
openshift-cherrypick-robot wants to merge 1 commit intoopenshift:release-4.18from
openshift-cherrypick-robot:cherry-pick-43-to-release-4.18
Open

[release-4.18] ART-13476: stop installing rpms that are already in the base image#47
openshift-cherrypick-robot wants to merge 1 commit intoopenshift:release-4.18from
openshift-cherrypick-robot:cherry-pick-43-to-release-4.18

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #43

/assign lgarciaaco

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 21, 2025

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: ART-13476

Details

In response to this:

This is an automated cherry-pick of #43

/assign lgarciaaco

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 openshift-ci bot requested review from arkadeepsen and jsafrane July 21, 2025 18:27
@dobsonj
Copy link
Member

dobsonj commented Jul 21, 2025

/lgtm
/approve
/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 Jul 21, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 21, 2025
@openshift-ci
Copy link

openshift-ci bot commented Jul 21, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dobsonj, openshift-cherrypick-robot

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 Jul 21, 2025
@duanwei33 duanwei33 removed their assignment Jul 23, 2025
@chiragkyal
Copy link
Member

/retest

@openshift-ci
Copy link

openshift-ci bot commented Jul 31, 2025

@openshift-cherrypick-robot: 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-vault ba92100 link false /test e2e-vault

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.

@duanwei33
Copy link

/unassign @Phaow @chao007 @ropatil010 @radeore @duanwei33

@emmajiafan
Copy link

/retest-required

@openshift-bot
Copy link

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

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 22, 2026
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. lgtm Indicates that a PR is ready to be merged. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Projects

None yet

Development

Successfully merging this pull request may close these issues.