openshift
[release-4.16] USHIFT-3318: Re-Enable Non-Upgrade Scenarios Which Depend on 4.17 mirrored rpms
This is an automated cherry-pick of #3470
/assign copejon
@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: USHIFT-3319
In response to this:
This is an automated cherry-pick of #3470
/assign copejon
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.
/retitle [release-4.16] USHIFT-3318: Re-Enable Non-Upgrade Scenarios Which Depend on 4.17 mirrored rpms
@openshift-cherrypick-robot: This pull request references USHIFT-3318 which is a valid jira issue.
In response to this:
This is an automated cherry-pick of #3470
/assign copejon
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.
For some reason, the PREVIOUS_RELEASE_REPO value is not being expanded when extract_container_images is called. The results is that the dnf download command inside extract_container_images is called without specifying the repo. It's weird, because the PREVIOUS_RELEASE_REPO value is calculated and set prior to the call.
This is also reproducible locally.
@copejon: Can not set label cherry-pick-approved: Must be member in one of these teams: []
In response to this:
/lgtm /label cherry-pick-approved
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] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: copejon, openshift-cherrypick-robot
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [copejon]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@openshift-cherrypick-robot: 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.