[release-4.12] OCPBUGS-34548: Use centos7 tag for quay.io/centos7/httpd-24-centos7 image by openshift-cherrypick-robot · Pull Request #1068 · openshift/cluster-ingress-operator

openshift-cherrypick-robot · 2024-05-28T18:01:24Z

This is an automated cherry-pick of #1065

/assign candita

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-ci-robot · 2024-05-28T18:01:33Z

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

Details

In response to this:

This is an automated cherry-pick of #1065

/assign candita

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-robot · 2024-05-28T18:01:51Z

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-34548, 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"
expected dependent Jira Issue OCPBUGS-34476 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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:

This is an automated cherry-pick of #1065

/assign candita

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.

candita · 2024-05-28T18:03:09Z

/approve
/lgtm

As noted on #1058 (comment), this change only affects test code and is low risk.
/label backport-risk-assessed

openshift-ci · 2024-05-28T18:03:39Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: candita

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:

~~OWNERS~~ [candita]

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

candita · 2024-05-28T18:04:38Z

unit failure:

could not run steps: step [input:root] failed: failed to wait for importing imagestreamtags on ci-op-rbn3xfhd/pipeline: failed to reimport the tag ci-op-rbn3xfhd/pipeline:ocp-4.12-upi-installer: unable to import tag ci-op-rbn3xfhd/pipeline:ocp-4.12-upi-installer with message dockerimage.image.openshift.io "quay.io/openshift/ci:ci-op-rbn3xfhd_pipeline_ocp-4.12-upi-installer" not found on the image stream even after (6) imports: timed out waiting for the condition

hongkailiu · 2024-05-28T18:34:00Z

/test all

candita · 2024-05-28T19:27:08Z

/test verify

candita · 2024-05-28T19:31:17Z

images failure could be temporary:

�[36mINFO�[0m[2024-05-28T18:49:23Z] Creating release image registry.build09.ci.openshift.org/ci-op-grn14xbv/release:latest.
�[36mINFO�[0m[2024-05-28T18:49:50Z] Ran for 15m23s
�[31mERRO�[0m[2024-05-28T18:49:50Z] Some steps failed:
�[31mERRO�[0m[2024-05-28T18:49:50Z]

could not run steps: step [release:latest] failed: release "release-latest" failed: could not watch pod: the pod ci-op-grn14xbv/release-latest failed after 27s (failed containers: ): ContainerFailed one or more containers exited

/test images

candita · 2024-05-28T22:04:37Z

Hoping this is temporary:

release "release-latest" failed: could not watch pod: the pod ci-op-grn14xbv/release-latest failed after 27s (failed containers: ): ContainerFailed one or more containers exited
/test e2e-gcp-ovn-serial

candita · 2024-05-28T22:05:21Z

/test e2e-azure-ovn

candita · 2024-05-28T22:08:05Z

/jira refresh

openshift-ci-robot · 2024-05-28T22:08:09Z

@candita: This pull request references Jira Issue OCPBUGS-34548, which is invalid:

expected dependent Jira Issue OCPBUGS-34476 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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.

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.

candita · 2024-05-29T00:46:02Z

Cluster install failure:

level=error msg=2024-05-28T22:17:57.483Z [INFO] Failed to read plugin lock file /tmp/installer/terraform/.terraform/plugins/linux_amd64/lock.json: open /tmp/installer/terraform/.terraform/plugins/linux_amd64/lock.json: no such file or directory

/jira refresh
/test e2e-gcp-ovn-serial

openshift-ci-robot · 2024-05-29T00:46:06Z

@candita: This pull request references Jira Issue OCPBUGS-34548, which is invalid:

expected dependent Jira Issue OCPBUGS-34476 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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.

Details

In response to this:

Cluster install failure:

level=error msg=2024-05-28T22:17:57.483Z [INFO] Failed to read plugin lock file /tmp/installer/terraform/.terraform/plugins/linux_amd64/lock.json: open /tmp/installer/terraform/.terraform/plugins/linux_amd64/lock.json: no such file or directory

/jira refresh
/test e2e-gcp-ovn-serial

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 · 2024-05-29T01:33:07Z

/jira refresh

openshift-ci-robot · 2024-05-29T01:33:14Z

@lihongan: This pull request references Jira Issue OCPBUGS-34548, 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.12.z) matches configured target version for branch (4.12.z)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
release note text is set and does not match the template
dependent bug Jira Issue OCPBUGS-34476 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-34476 targets the "4.13.z" version, which is one of the valid target versions: 4.13.0, 4.13.z
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.

lihongan · 2024-05-29T01:33:48Z

/label qe-approved
/label cherry-pick-approved

openshift-ci-robot · 2024-05-29T01:33:54Z

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

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.12.z) matches configured target version for branch (4.12.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note text is set and does not match the template
dependent bug Jira Issue OCPBUGS-34476 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-34476 targets the "4.13.z" version, which is one of the valid target versions: 4.13.0, 4.13.z
bug has dependents

Requesting review from QA contact:
/cc @lihongan

Details

In response to this:

This is an automated cherry-pick of #1065

/assign candita

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-robot · 2024-05-29T03:58:35Z

/retest-required

Remaining retests: 0 against base HEAD 5e62d56 and 2 for PR HEAD 300935b in total

candita · 2024-05-29T18:17:31Z

Oauth failure not related to this change:

....{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"forbidden: User "system:anonymous" cannot get path "/metrics"","reason":"Forbidden","details":{},"code":403}

Expected
: 403 Forbidden
to contain substring
: 401 Unauthorized

/test e2e-gcp-ovn-serial

rfredette · 2024-05-30T14:36:26Z

test failures are unrelated.
/retest

openshift-ci · 2024-05-30T17:02:01Z

@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-ci-robot · 2024-05-30T17:05:20Z

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

openshift/cluster-ingress-operator#1068

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

Details

In response to this:

This is an automated cherry-pick of #1065

/assign candita

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 · 2024-05-30T18:49:38Z

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-cluster-ingress-operator-container-v4.12.0-202405301737.p0.ga1812c5.assembly.stream.el8 for distgit ose-cluster-ingress-operator.
All builds following this will include this PR.

openshift-merge-robot · 2024-05-31T03:50:43Z

Fix included in accepted release 4.12.0-0.nightly-2024-05-30-225315

openshift-cherrypick-robot mentioned this pull request May 28, 2024

[release-4.13] OCPBUGS-34476: Use centos7 tag for quay.io/centos7/httpd-24-centos7 image #1065

Merged

openshift-cherrypick-robot assigned candita May 28, 2024

openshift-ci bot changed the title ~~[release-4.12] OCPBUGS-34476: Use centos7 tag for quay.io/centos7/httpd-24-centos7 image~~ [release-4.12] OCPBUGS-34548: Use centos7 tag for quay.io/centos7/httpd-24-centos7 image May 28, 2024

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 28, 2024

openshift-ci bot requested review from Miciah and miheer May 28, 2024 18:02

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 28, 2024

openshift-ci bot assigned lihongan, melvinjoseph86 and ShudiLi May 28, 2024

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 28, 2024

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 28, 2024

openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label May 29, 2024

openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label May 29, 2024

openshift-ci bot requested a review from lihongan May 29, 2024 01:33

openshift-ci bot added qe-approved Signifies that QE has signed off on this PR cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. labels May 29, 2024

openshift-merge-bot bot merged commit a1812c5 into openshift:release-4.12 May 30, 2024

Comments

Conversation

openshift-cherrypick-robot commented May 28, 2024

Uh oh!

openshift-ci-robot commented May 28, 2024

Uh oh!

openshift-ci-robot commented May 28, 2024

Uh oh!

candita commented May 28, 2024

Uh oh!

openshift-ci bot commented May 28, 2024

Uh oh!

candita commented May 28, 2024

Uh oh!

hongkailiu commented May 28, 2024

Uh oh!

candita commented May 28, 2024

Uh oh!

candita commented May 28, 2024

Uh oh!

candita commented May 28, 2024

Uh oh!

candita commented May 28, 2024

Uh oh!

candita commented May 28, 2024

Uh oh!

openshift-ci-robot commented May 28, 2024

Uh oh!

candita commented May 29, 2024

Uh oh!

openshift-ci-robot commented May 29, 2024

Uh oh!

lihongan commented May 29, 2024

Uh oh!

openshift-ci-robot commented May 29, 2024

Uh oh!

lihongan commented May 29, 2024

Uh oh!

openshift-ci-robot commented May 29, 2024

Uh oh!

openshift-ci-robot commented May 29, 2024

Uh oh!

candita commented May 29, 2024

Uh oh!

rfredette commented May 30, 2024

Uh oh!

openshift-ci bot commented May 30, 2024

Uh oh!

openshift-ci-robot commented May 30, 2024

Uh oh!

openshift-bot commented May 30, 2024

Uh oh!

openshift-merge-robot commented May 31, 2024

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

10 participants