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-50916: managed services: add hcp crd to unstable list #29460

Merged
merged 1 commit into from
Jan 24, 2025

Conversation

jbpratt
Copy link
Contributor

@jbpratt jbpratt commented Jan 21, 2025

Signed-off-by: Brady Pratt [email protected]

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 21, 2025
@openshift-ci-robot
Copy link

@jbpratt: This pull request explicitly references no jira issue.

In response to this:

Signed-off-by: Brady Pratt [email protected]

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 review from bparees and sdodson January 21, 2025 17:10
@stbenjam
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 21, 2025
Copy link
Contributor

openshift-ci bot commented Jan 21, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jbpratt, stbenjam

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 Jan 21, 2025
@jbpratt
Copy link
Contributor Author

jbpratt commented Jan 22, 2025

/retest-required

@stbenjam
Copy link
Member

/label acknowledge-critical-fixes-only

@openshift-ci openshift-ci bot added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Jan 22, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 618ea1c and 2 for PR HEAD 052475e in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 4b05413 and 1 for PR HEAD 052475e in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 4b05413 and 2 for PR HEAD 052475e in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 4ca8255 and 2 for PR HEAD 052475e in total

Copy link

openshift-trt bot commented Jan 23, 2025

Job Failure Risk Analysis for sha: 052475e

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-serial Medium
[sig-imageregistry][Serial] Image signature workflow can push a signed image to openshift registry and verify it [apigroup:user.openshift.io][apigroup:image.openshift.io] [Skipped:Disconnected] [Suite:openshift/conformance/serial]
This test has passed 96.46% of 424 runs on release 4.19 [Overall] in the last week.

@jbpratt
Copy link
Contributor Author

jbpratt commented Jan 23, 2025

/test e2e-aws-ovn-serial

Copy link
Contributor

openshift-ci bot commented Jan 23, 2025

@jbpratt: 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-aws-ovn-upgrade 052475e link false /test e2e-aws-ovn-upgrade
ci/prow/e2e-aws-ovn-single-node-serial 052475e link false /test e2e-aws-ovn-single-node-serial
ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout 052475e link false /test e2e-metal-ipi-ovn-kube-apiserver-rollout
ci/prow/okd-scos-e2e-aws-ovn 052475e link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-metal-ipi-ovn 052475e link false /test e2e-metal-ipi-ovn
ci/prow/e2e-aws-ovn-single-node 052475e link false /test e2e-aws-ovn-single-node

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-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD a30e8f6 and 2 for PR HEAD 052475e in total

@openshift-merge-bot openshift-merge-bot bot merged commit 5b828df into openshift:master Jan 24, 2025
23 of 29 checks passed
@jbpratt jbpratt deleted the hcp-unstable-api branch January 24, 2025 14:05
@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-tests
This PR has been included in build openshift-enterprise-tests-container-v4.19.0-202501241437.p0.g5b828df.assembly.stream.el9.
All builds following this will include this PR.

@jbpratt
Copy link
Contributor Author

jbpratt commented Feb 14, 2025

/cherrypick release-4.18

@jbpratt
Copy link
Contributor Author

jbpratt commented Feb 14, 2025

/cherry-pick release-4.18

@openshift-cherrypick-robot

@jbpratt: new pull request created: #29542

In response to this:

/cherrypick release-4.18

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

@jbpratt: new pull request could not be created: failed to create pull request against openshift/origin#release-4.18 from head openshift-cherrypick-robot:cherry-pick-29460-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-29460-to-release-4.18."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

In response to this:

/cherry-pick release-4.18

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.

@jbpratt
Copy link
Contributor Author

jbpratt commented Feb 17, 2025

@jbpratt jbpratt changed the title NO-JIRA: managed services: add hcp crd to unstable list OCPBUGS-50916: managed services: add hcp crd to unstable list Feb 17, 2025
@openshift-ci-robot
Copy link

@jbpratt: Jira Issue OCPBUGS-50916: All pull requests linked via external trackers have merged:

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

In response to this:

Signed-off-by: Brady Pratt [email protected]

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.

@jbpratt
Copy link
Contributor Author

jbpratt commented Feb 17, 2025

/cherrypick release-4.18

@jbpratt
Copy link
Contributor Author

jbpratt commented Feb 17, 2025

/cherry-pick release-4.18

@openshift-cherrypick-robot

@jbpratt: new pull request created: #29545

In response to this:

/cherrypick release-4.18

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

@jbpratt: new pull request could not be created: failed to create pull request against openshift/origin#release-4.18 from head openshift-cherrypick-robot:cherry-pick-29460-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-29460-to-release-4.18."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

In response to this:

/cherry-pick release-4.18

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
acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. 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