OCPBUGS-66250: Replace terraform-provider-google with Openshift fork#10144
OCPBUGS-66250: Replace terraform-provider-google with Openshift fork#10144sdodson merged 1 commit intoopenshift:release-4.12from
Conversation
openshift-ci-robot
added
jira/valid-reference
|
@sunku5494: This pull request references Jira Issue OCPBUGS-66250, 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. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/retest-required |
barbacbd
left a comment
barbacbd
left a comment
There was a problem hiding this comment.
Similar to the 4.13 PR, The following issue is observed in the tests
error: unable to create a release: operator "cluster-cloud-controller-manager-operator" contained an invalid image-references file: no input image tag named "openstack-cloud-controller-manager"
@patrickdillon is this something new we are referencing or something that was removed?
|
/retest |
2 similar comments
|
/retest |
|
/retest |
|
/retest-required ci/prow/e2e-gcp-ovn passed 🟢 |
|
@sunku5494: 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. |
|
/jira refresh |
|
@sdodson: This pull request references Jira Issue OCPBUGS-66250, 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. |
|
/jira refresh |
openshift-ci-robot
added
jira/valid-bug
|
@sdodson: This pull request references Jira Issue OCPBUGS-66250, 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. |
|
@tthvo mind reviewing, i'm hoping that once we get this in the 4.13 jobs which install 4.12 first will start passing again. |
tthvo
left a comment
tthvo
left a comment
There was a problem hiding this comment.
/lgtm
/verified by e2e-gcp-ovn
The vendor shows the necessary changes. LGTM!
|
/tide refresh |
|
/payload-job periodic-ci-openshift-release-master-ci-4.13-upgrade-from-stable-4.12-e2e-gcp-ovn-rt-upgrade |
|
@tthvo: 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/0d70e0e0-dbcf-11f0-8437-104db454027f-0 |
|
/test ci/prow/e2e-gcp-ovn-byo-vpc |
|
@tthvo: The specified target(s) for 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. |
|
/test e2e-gcp-ovn-byo-vpc |
Hey @sdodson, I am guessing you meant, for example, this job: #10144 (comment) so I launched one to double check 👀 I applied the lgtm (and later verified). Maybe you can help with the rest of the labels? |
|
😓 The payload testing failed with the same error... Maybe, the change didn't apply because the job is meant to upgrade from a released 4.12.z? I think the presubmit passed so I am OK if we add |
|
/label approved backport-risk-assessed |
openshift-ci-robot
added
the
verified
|
@sdodson: 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. |
|
/label approved backport-risk-assessed |
|
@sunku5494: Jira Issue Verification Checks: Jira Issue OCPBUGS-66250 Jira Issue OCPBUGS-66250 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓 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. |
|
Fix included in accepted release 4.12.0-0.nightly-2025-12-18-192430 |
7 participants
/assign @sunku5494