Skip to content

[WIP] WRKLDS-1449: bump openshift/api and bring in ObjectMeta for authorization and security types#29067

Closed
atiratree wants to merge 3 commits intoopenshift:masterfrom
atiratree:metadata-bump
Closed

[WIP] WRKLDS-1449: bump openshift/api and bring in ObjectMeta for authorization and security types#29067
atiratree wants to merge 3 commits intoopenshift:masterfrom
atiratree:metadata-bump

Conversation

@atiratree
Copy link
Copy Markdown
Member

No description provided.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 5, 2024
@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 5, 2024
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Sep 5, 2024

@atiratree: This pull request references WRKLDS-1449 which is a valid jira issue.

Details

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.

@openshift-ci openshift-ci Bot added the vendor-update Touching vendor dir or related files label Sep 5, 2024
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Sep 5, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: atiratree
Once this PR has been reviewed and has the lgtm label, please assign neisw for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details 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

@bertinatto
Copy link
Copy Markdown
Member

/retest

1 similar comment
@atiratree
Copy link
Copy Markdown
Member Author

/retest

@openshift-trt-bot
Copy link
Copy Markdown

Job Failure Risk Analysis for sha: 2789a2c

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-upgrade Medium
[Jira:"Test Framework"] monitor test lease-checker interval construction
This test has passed 96.07% of 305 runs on jobs ['periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-upgrade'] in the last 14 days.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 8, 2024
@openshift-merge-robot
Copy link
Copy Markdown
Contributor

PR needs rebase.

Details

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-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Oct 1, 2024

@atiratree: 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-single-node-upgrade 2789a2c link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-ovn-kube-apiserver-rollout 2789a2c link false /test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-aws-ovn-ipsec-serial 2789a2c link false /test e2e-aws-ovn-ipsec-serial
ci/prow/e2e-aws-ovn-serial 2789a2c link true /test e2e-aws-ovn-serial
ci/prow/e2e-aws-ovn-upgrade 2789a2c link false /test e2e-aws-ovn-upgrade
ci/prow/e2e-gcp-ovn-builds 2789a2c link true /test e2e-gcp-ovn-builds

Full PR test history. Your PR dashboard.

Details

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.

@atiratree
Copy link
Copy Markdown
Member Author

already included in #29103

@atiratree atiratree closed this Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. vendor-update Touching vendor dir or related files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants