New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OCPBUGS-28231: Guard upgrading GCP from 4.14 to 4.15 without RoleAdmin permissions #670
OCPBUGS-28231: Guard upgrading GCP from 4.14 to 4.15 without RoleAdmin permissions #670
Conversation
@jstuever: This pull request references Jira Issue OCPBUGS-28231, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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. |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## release-4.14 #670 +/- ##
================================================
+ Coverage 48.41% 48.57% +0.16%
================================================
Files 96 96
Lines 11744 11839 +95
================================================
+ Hits 5686 5751 +65
- Misses 5427 5453 +26
- Partials 631 635 +4
|
/test e2e-gcp |
/payload-job periodic-ci-openshift-release-master-ci-4.15-e2e-gcp-ovn-upgrade-out-of-change |
@jstuever: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/703b0f70-c213-11ee-9c68-93c96ebcc1b3-0 |
35692dc
to
781b0ca
Compare
/retest |
/retest-required |
/payload-job periodic-ci-openshift-release-master-ci-4.14-e2e-gcp-ovn-upgrade-out-of-change |
/payload-job periodic-ci-openshift-release-master-ci-4.15-e2e-gcp-ovn-upgrade-out-of-change |
@jstuever: trigger 0 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command |
@jstuever: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/620b17a0-c525-11ee-93e5-a255d268e3c8-0 |
@jstuever: This pull request references Jira Issue OCPBUGS-28231, which is invalid:
Comment 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. |
/jira refresh |
@jstuever: This pull request references Jira Issue OCPBUGS-28231, which is invalid:
Comment 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. |
/jira refresh |
@jstuever: This pull request references Jira Issue OCPBUGS-28231, which is invalid:
Comment 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. |
/label backport-risk-assessed |
/jira refresh |
@jstuever: This pull request references Jira Issue OCPBUGS-28231, which is valid. The bug has been moved to the POST state. 6 validation(s) were run on this bug
Requesting review from QA contact: 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. |
/assign @dlom |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dlom, jstuever 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 |
It is my understanding that the dev ci jobs use openshift-e2e-test for upgrades, which will use the --force option as per the code here. |
QE's upgrade step update done. |
@jstuever: 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/test-infra repository. I understand the commands that are listed here. |
007cd00
into
openshift:release-4.14
@jstuever: Jira Issue OCPBUGS-28231: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-28231 has been moved to the MODIFIED state. 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. |
[ART PR BUILD NOTIFIER] This PR has been included in build ose-cloud-credential-operator-container-v4.14.0-202402190838.p0.g007cd00.assembly.stream.el8 for distgit ose-cloud-credential-operator. |
Fix included in accepted release 4.14.0-0.nightly-2024-02-19-170131 |
After adding granular permissions to the GCP platform in 4.15, new permission are required on the root credential service account. The GCP platform in mint mode now requires the upgradeable annotation to upgrade from 4.14.x to a newer minor version such as 4.15.0.
This PR should only be applied to 4.14.