Skip to content
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-51373,OCPBUGS-44671: Updates GCP credentials request #1335

Merged

Conversation

theobarberbany
Copy link
Contributor

This change adds the compute.images.get and getFromFamily to the credentials request for GCP. It is required by MAPG for checking if a disk is UEFI compatible.

See openshift/machine-api-provider-gcp#108

This change adds the compute.images.get and getFromFamily to the
credentials request for GCP. It is required by MAPG for checking if a
disk is UEFI compatible.

See openshift/machine-api-provider-gcp#108
@openshift-ci openshift-ci bot requested review from elmiko and racheljpg February 27, 2025 12:41
@theobarberbany theobarberbany changed the title Updates GCP credentials request OCPBUGS-51373, :Updates GCP credentials request Feb 27, 2025
@theobarberbany
Copy link
Contributor Author

/payload job periodic-ci-openshift-release-master-ci-4.19-e2e-gcp-ovn-techpreview-serial

Copy link
Contributor

openshift-ci bot commented Feb 27, 2025

@theobarberbany: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.

@theobarberbany
Copy link
Contributor Author

/payload-job periodic-ci-openshift-release-master-ci-4.19-e2e-gcp-ovn-techpreview-serial

Copy link
Contributor

openshift-ci bot commented Feb 27, 2025

@theobarberbany: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-ci-4.19-e2e-gcp-ovn-techpreview-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/28db3f30-f50a-11ef-94c7-090ce508aedf-0

@theobarberbany theobarberbany changed the title OCPBUGS-51373, :Updates GCP credentials request OCPBUGS-51373,OCPBUGS-44671: Updates GCP credentials request Feb 27, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 27, 2025
@openshift-ci-robot
Copy link
Contributor

@theobarberbany: This pull request references Jira Issue OCPBUGS-51373, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sunzhaohua2

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-44671, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Verified instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This change adds the compute.images.get and getFromFamily to the credentials request for GCP. It is required by MAPG for checking if a disk is UEFI compatible.

See openshift/machine-api-provider-gcp#108

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 openshift-ci bot requested a review from sunzhaohua2 February 27, 2025 12:56
@theobarberbany
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 27, 2025
@openshift-ci-robot
Copy link
Contributor

@theobarberbany: This pull request references Jira Issue OCPBUGS-51373, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sunzhaohua2

This pull request references Jira Issue OCPBUGS-44671, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @miyadav

In response to this:

/jira refresh

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 openshift-ci bot requested a review from miyadav February 27, 2025 12:58
@JoelSpeed
Copy link
Contributor

/lgtm
/approve
/hold for testing

Theo, feel free to release the hold if you're confident the tests pass

Given the serial perma-failed, this should be pretty binary on if this fixes it or not

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 27, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 27, 2025
Copy link
Contributor

openshift-ci bot commented Feb 27, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 27, 2025
@JoelSpeed
Copy link
Contributor

CI suggests this isn't actually fixing the issue, but I think this is the correct to merge still, even if it doesn't resolve the issue

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 27, 2025
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD dc56fbf and 2 for PR HEAD f383616 in total

Copy link
Contributor

openshift-ci bot commented Feb 27, 2025

@theobarberbany: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-metal-ipi f383616 link false /test e2e-metal-ipi
ci/prow/okd-scos-e2e-aws-ovn f383616 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-openstack f383616 link false /test e2e-openstack
ci/prow/e2e-vsphere-ovn-serial f383616 link false /test e2e-vsphere-ovn-serial
ci/prow/e2e-metal-ipi-upgrade f383616 link false /test e2e-metal-ipi-upgrade
ci/prow/e2e-metal-ipi-ovn-dualstack f383616 link false /test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-nutanix f383616 link false /test e2e-nutanix
ci/prow/e2e-metal-ipi-virtualmedia f383616 link false /test e2e-metal-ipi-virtualmedia

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 709f4c3 into openshift:master Feb 27, 2025
21 of 29 checks passed
@openshift-ci-robot
Copy link
Contributor

@theobarberbany: Jira Issue OCPBUGS-51373: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-51373 has been moved to the MODIFIED state.

Jira Issue OCPBUGS-44671: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-44671 has been moved to the MODIFIED state.

In response to this:

This change adds the compute.images.get and getFromFamily to the credentials request for GCP. It is required by MAPG for checking if a disk is UEFI compatible.

See openshift/machine-api-provider-gcp#108

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-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-machine-api-operator
This PR has been included in build ose-machine-api-operator-container-v4.19.0-202502272240.p0.g709f4c3.assembly.stream.el9.
All builds following this will include this PR.

@theobarberbany
Copy link
Contributor Author

/cherry-pick release-4.18 release-4.17 release-4.16 release-4.15 release-4.14 release-4.13

@openshift-cherrypick-robot

@theobarberbany: new pull request created: #1341

In response to this:

/cherry-pick release-4.18 release-4.17 release-4.16 release-4.15 release-4.14 release-4.13

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-cherrypick-robot

@theobarberbany: new pull request could not be created: failed to create pull request against openshift/machine-api-operator#release-4.18 from head openshift-cherrypick-robot:cherry-pick-1335-to-release-4.18: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for openshift-cherrypick-robot:cherry-pick-1335-to-release-4.18."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

In response to this:

/cherrypick release-4.18 release-4.17 release-4.16 release-4.15 release-4.14 release-4.13

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants