[release-4.16] OCPBUGS-43967: Revendor assisted service external platform oci#9150
Conversation
|
@pawanpinjarkar: This pull request references Jira Issue OCPBUGS-43967, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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. |
|
/jira refresh |
|
@pawanpinjarkar: This pull request references Jira Issue OCPBUGS-43967, which is invalid:
Comment 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. |
|
/retest-required |
|
I'm wondering why verify-vendor is failing. It doesn't look like a sporadic issue. |
|
/retest-required |
|
@pawanpinjarkar: The following test 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. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bfournie 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 |
|
/jira refresh |
|
@pawanpinjarkar: This pull request references Jira Issue OCPBUGS-43967, which is valid. The bug has been moved to the POST state. 7 validation(s) were run on this bug
Requesting review from QA contact: 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. |
|
This is revendoring to the same commit as the 4.17 PR, which is presumably in the 4.17 (or worse, 4.18) branch. That seems risky to me as it will pick up far more commits than we are intending, with unknown consequences. |
in 4.17 PR, we only revendored this specific commit openshift/assisted-service@d41f536 If it is safer to not cherrypick from 4.17 but do a seperate revendoring of assisted-service in 4.16 (this specific commit openshift/assisted-service@d41f536 ), I can close this PR and open a new one. |
|
The specific point we are revendoring to (openshift/assisted-service@6573b5d7021d) is already part of the release-4.16 branch, so we are not pulling in any changes to assisted-service that post-date this release. A manual review of the diff shows nothing too alarming. |
|
/label cherry-pick-approved |
|
/lgtm |
|
@pawanpinjarkar: Jira Issue OCPBUGS-43967: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-43967 has been moved to the MODIFIED state. 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. |
|
[ART PR BUILD NOTIFIER] Distgit: ose-baremetal-installer |
|
[ART PR BUILD NOTIFIER] Distgit: ose-installer-altinfra |
|
[ART PR BUILD NOTIFIER] Distgit: ose-installer-terraform-providers |
|
[ART PR BUILD NOTIFIER] Distgit: ose-installer-artifacts |
Manual cherry-pick of #9147