[release-4.21] USHIFT-6423: Add release info images into the mirrored registry#6066
Conversation
|
@ggiguash: This pull request references USHIFT-6423 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 bug to target either version "4.21." or "openshift-4.21.", but it targets "openshift-4.22" instead. DetailsIn response to this: 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
bot
added
the
do-not-merge/work-in-progress
openshift-ci-robot
added
the
jira/valid-reference
|
Skipping CI for Draft Pull Request. |
|
/test ? |
|
@ggiguash: The following commands are available to trigger required jobs: The following commands are available to trigger optional jobs: Use DetailsIn response to this:
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-ci
bot
added
the
approved
|
/test e2e-aws-tests-release |
|
/test e2e-aws-tests-cache |
1 similar comment
|
/test e2e-aws-tests-cache |
ggiguash
force-pushed
the
ci-optimizations-421
branch
from
75b04b8 to
0aa2e36
Compare
|
/test e2e-aws-tests-cache |
|
/test e2e-aws-tests-release |
openshift-ci
bot
removed
the
do-not-merge/work-in-progress
|
|
||
| ``` | ||
| sudo dnf install -y podman podman-compose | ||
| sudo dnf install -y podman podman-docker podman-compose |
There was a problem hiding this comment.
Why do we install podman-docker? I don't see any commands that would require docker.sock from podman
There was a problem hiding this comment.
Ah, this comes from when I revisited quay rebuild procedure. It turns out they use docker-composer for builds so we need to install podman-docker to allow for successful quay builds
|
/lgtm |
|
The situation with release tests improved a lot. We have el100 failing, which is the only systemic failure remaining. Others are specific test failures. All of this will be investigated and resolved in the follow-up PRs /label backport-risk-assessed |
openshift-ci
bot
added
backport-risk-assessed
openshift-ci-robot
added
the
verified
|
@ggiguash: This PR has been marked as verified by DetailsIn response to this:
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. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ggiguash, pmtk The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Overriding the failed jobs to make progress. The remaining issues will be addressed in a follow-up PR. /override ci/prow/e2e-aws-tests ci/prow/e2e-aws-tests-bootc-periodic ci/prow/e2e-aws-tests-bootc-periodic-arm ci/prow/e2e-aws-tests-bootc-release ci/prow/e2e-aws-tests-bootc-release-arm ci/prow/e2e-aws-tests-release |
|
@ggiguash: Overrode contexts on behalf of ggiguash: ci/prow/e2e-aws-tests, ci/prow/e2e-aws-tests-bootc-periodic, ci/prow/e2e-aws-tests-bootc-periodic-arm, ci/prow/e2e-aws-tests-bootc-release, ci/prow/e2e-aws-tests-bootc-release-arm, ci/prow/e2e-aws-tests-release DetailsIn response to this:
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. |
|
/override ci/prow/e2e-aws-tests |
|
@ggiguash: Overrode contexts on behalf of ggiguash: ci/prow/e2e-aws-tests DetailsIn response to this:
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. |
|
@ggiguash: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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
bot
merged commit 88ba964
into
openshift:release-4.21
3 participants
No description provided.