USHIFT-3319: Re-Enable Non-Upgrade Scenarios Which Depend on 4.17 mirrored rpms #3470
Conversation
|
/cherry-pick release-4.16 |
|
@copejon: once the present PR merges, I will cherry-pick it on top of release-4.16 in a new PR and assign it to you. In 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
copejon
changed the title
|
/retest |
|
@copejon: No Jira issue is referenced in the title of this pull request. In 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. |
copejon
changed the title
|
@copejon: This pull request references USHIFT-3319 which is a valid jira issue. In 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-robot
added
the
jira/valid-reference
copejon
force-pushed
the
ushift-3319
branch
3 times, most recently
from
2d09ace
to
f31a278
Compare
|
FIPs scenarios are currently broken and are blocking this PR from merging. See this PR's jira ticket for more information |
copejon
force-pushed
the
ushift-3319
branch
2 times, most recently
from
696bb27
to
9d7b5c8
Compare
…he public mirror Signed-off-by: Jon Cope <jcope@redhat.com>
copejon
changed the title
|
@copejon: This pull request references USHIFT-3319 which is a valid jira issue. In 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. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: copejon, ggiguash The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@ggiguash: Overrode contexts on behalf of ggiguash: ci/prow/metal-periodic-test In 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. |
|
@copejon: all tests passed! Full PR test history. Your PR dashboard. 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. |
|
@copejon: new pull request created: #3511 In 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. |
Upgrade tests are handled by PR #3506