Skip to content

[release-4.15] OCPBUGS-34252: Use centos7 tag for quay.io/centos7/httpd-24-centos7 image#1058

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.15from
openshift-cherrypick-robot:cherry-pick-1037-to-release-4.15
May 23, 2024
Merged

[release-4.15] OCPBUGS-34252: Use centos7 tag for quay.io/centos7/httpd-24-centos7 image#1058
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.15from
openshift-cherrypick-robot:cherry-pick-1037-to-release-4.15

Conversation

@openshift-cherrypick-robot
Copy link

@openshift-cherrypick-robot openshift-cherrypick-robot commented May 22, 2024

This is an automated cherry-pick of #1037

/assign rfredette

/cherrypick release-4.14 release-4.13 release-4.12

@rfredette
Use centos7 tag for quay.io/centos7/httpd-24-centos7 image
e5d4c1b 
The latest tag for quay.io/centos7/httpd-24-centos7 is no longer
available, but the same image is accessible with the centos7 tag. In the
long term, a different httpd image should probably be used, but this
change should get tests passing.

This is a fix for OCPBUGS-31722.

https://issues.redhat.com//browse/OCPBUGS-31722
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request May 22, 2024
Merged
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented May 22, 2024

@openshift-cherrypick-robot: Jira Issue OCPBUGS-31722 has been cloned as Jira Issue OCPBUGS-34252. Will retitle bug to link to clone.
/retitle [release-4.15] OCPBUGS-34252: Use centos7 tag for quay.io/centos7/httpd-24-centos7 image

Details

In response to this:

This is an automated cherry-pick of #1037

/assign rfredette

/cherrypick release-4.14 release-4.13 release-4.12

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 changed the title [release-4.15] OCPBUGS-31722: Use centos7 tag for quay.io/centos7/httpd-24-centos7 image [release-4.15] OCPBUGS-34252: Use centos7 tag for quay.io/centos7/httpd-24-centos7 image May 22, 2024
@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 May 22, 2024
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented May 22, 2024

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-34252, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"

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:

This is an automated cherry-pick of #1037

/assign rfredette

/cherrypick release-4.14 release-4.13 release-4.12

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.

@rfredette
Copy link
Contributor

rfredette commented May 22, 2024

/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 May 22, 2024
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented May 22, 2024

@rfredette: This pull request references Jira Issue OCPBUGS-34252, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.15.z) matches configured target version for branch (4.15.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-31722 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-31722 targets the "4.16.0" version, which is one of the valid target versions: 4.16.0
  • bug has dependents

Requesting review from QA contact:
/cc @lihongan

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.

@openshift-ci openshift-ci bot requested review from frobware, knobunc and lihongan May 22, 2024 19:18
@candita
Copy link
Contributor

candita commented May 22, 2024

--- FAIL: TestCreateClusterProxy (2310.10s)

/retest-required

@Miciah
Copy link
Contributor

Miciah commented May 23, 2024

Thanks!
/approve
/lgtm
This change only affects test code and is low risk.
/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 May 23, 2024
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 23, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 23, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Miciah

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 May 23, 2024
@lihongan
Copy link
Contributor

lihongan commented May 23, 2024

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label May 23, 2024
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented May 23, 2024

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-34252, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.15.z) matches configured target version for branch (4.15.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-31722 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-31722 targets the "4.16.0" version, which is one of the valid target versions: 4.16.0
  • bug has dependents

Requesting review from QA contact:
/cc @lihongan

Details

In response to this:

This is an automated cherry-pick of #1037

/assign rfredette

/cherrypick release-4.14 release-4.13 release-4.12

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.

@lihongan
Copy link
Contributor

lihongan commented May 23, 2024

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label May 23, 2024
@lihongan
Copy link
Contributor

lihongan commented May 23, 2024

/test e2e-azure-operator

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented May 23, 2024

/retest-required

Remaining retests: 0 against base HEAD 0106cb9 and 2 for PR HEAD e5d4c1b in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 23, 2024

@openshift-cherrypick-robot: 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.

@openshift-merge-bot openshift-merge-bot bot merged commit 9fc0b5c into openshift:release-4.15 May 23, 2024
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented May 23, 2024

@openshift-cherrypick-robot: Jira Issue OCPBUGS-34252: All pull requests linked via external trackers have merged:

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

Details

In response to this:

This is an automated cherry-pick of #1037

/assign rfredette

/cherrypick release-4.14 release-4.13 release-4.12

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-bot
Copy link
Contributor

openshift-bot commented May 23, 2024

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-cluster-ingress-operator-container-v4.15.0-202405231336.p0.g9fc0b5c.assembly.stream.el9 for distgit ose-cluster-ingress-operator.
All builds following this will include this PR.

@candita
Copy link
Contributor

candita commented May 23, 2024

/cherry-pick release-4.14 release-4.13

@openshift-cherrypick-robot
Copy link
Author

openshift-cherrypick-robot commented May 23, 2024

@candita: new pull request created: #1061

Details

In response to this:

/cherry-pick release-4.14 release-4.13

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 openshift-cherrypick-robot mentioned this pull request May 23, 2024
Merged
@Miciah Miciah mentioned this pull request May 28, 2024
Merged
@candita candita mentioned this pull request May 28, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@lihongan lihongan Awaiting requested review from lihongan

@frobware frobware Awaiting requested review from frobware

@knobunc knobunc Awaiting requested review from knobunc

Assignees

@rfredette rfredette

@Miciah Miciah

@lihongan lihongan

@melvinjoseph86 melvinjoseph86

@ShudiLi ShudiLi

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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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. qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

9 participants

@openshift-cherrypick-robot @openshift-ci-robot @rfredette @candita @Miciah @lihongan @openshift-bot @melvinjoseph86 @ShudiLi