Skip to content

Comments

ART-13476: stop installing rpms that are already in the base image#43

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
lgarciaaco:fix/dockerfile
Jul 17, 2025
Merged

ART-13476: stop installing rpms that are already in the base image#43
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
lgarciaaco:fix/dockerfile

Conversation

@lgarciaaco
Copy link

@dobsonj
Copy link
Member

dobsonj commented Jul 17, 2025

@lgarciaaco the change looks good, but can you prepend the commit message with UPSTREAM: <carry>: to pass the verify-commits job?

@openshift-ci
Copy link

openshift-ci bot commented Jul 17, 2025

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

@dobsonj
Copy link
Member

dobsonj commented Jul 17, 2025

/retitle ART-13476: stop installing rpms that are already in the base image

@openshift-ci openshift-ci bot changed the title stop installing rpms that are already in the base image ART-13476: stop installing rpms that are already in the base image Jul 17, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 17, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 17, 2025

@lgarciaaco: This pull request references ART-13476 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.20.0" version, but no target version was set.

Details

In response to this:

https://issues.redhat.com/browse/ART-13476

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.

@dobsonj
Copy link
Member

dobsonj commented Jul 17, 2025

/lgtm
/approve
/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Jul 17, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 17, 2025

@lgarciaaco: This pull request references ART-13476 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.20.0" version, but no target version was set.

Details

In response to this:

https://issues.redhat.com/browse/ART-13476

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

openshift-ci bot commented Jul 17, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dobsonj, lgarciaaco

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 17, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 9152f5b into openshift:main Jul 17, 2025
9 checks passed
@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: ose-secrets-store-csi-driver
This PR has been included in build ose-secrets-store-csi-driver-container-v4.20.0-202507171216.p0.g9152f5b.assembly.stream.el9.
All builds following this will include this PR.

@lgarciaaco
Copy link
Author

/cherry-pick release-4.20
/cherry-pick release-4.19

@openshift-cherrypick-robot

@lgarciaaco: new pull request created: #44

Details

In response to this:

/cherry-pick release-4.20
/cherry-pick release-4.19

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.

@openshift-cherrypick-robot

@lgarciaaco: new pull request could not be created: failed to create pull request against openshift/secrets-store-csi-driver#release-4.20 from head openshift-cherrypick-robot:cherry-pick-43-to-release-4.20: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"No commits between openshift:release-4.20 and openshift-cherrypick-robot:cherry-pick-43-to-release-4.20"}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

Details

In response to this:

/cherry-pick release-4.20
/cherry-pick release-4.19

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.

@lgarciaaco
Copy link
Author

/cherry-pick release-4.18
/cherry-pick release-4.17

@openshift-cherrypick-robot

@lgarciaaco: new pull request created: #46

Details

In response to this:

/cherry-pick release-4.18
/cherry-pick release-4.17

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.

@openshift-cherrypick-robot

@lgarciaaco: new pull request created: #47

Details

In response to this:

/cherry-pick release-4.18
/cherry-pick release-4.17

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.

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-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants