Skip to content

WIP: CNTRLPLANE-333: Add generation logic for new uid and extra fields in the Authentication CR #763

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

everettraven
Copy link
Contributor

No description provided.

@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 Mar 17, 2025
@openshift-ci openshift-ci bot requested review from ibihim and liouk March 17, 2025 19:57
Copy link
Contributor

openshift-ci bot commented Mar 17, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

The full list of commands accepted by this bot can be found 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

@everettraven everettraven changed the title WIP: Add generation logic for new uid and extra fields in the Authentication CR WIP: CNTRLPLANE-333: Add generation logic for new uid and extra fields in the Authentication CR Mar 18, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 18, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 18, 2025

@everettraven: This pull request references CNTRLPLANE-333 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

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.

Copy link
Contributor

openshift-ci bot commented Mar 20, 2025

@everettraven: 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-single-node 1cedc4b link false /test e2e-aws-single-node
ci/prow/e2e-agnostic 1cedc4b link true /test e2e-agnostic
ci/prow/images 1cedc4b link true /test images
ci/prow/e2e-operator 1cedc4b link true /test e2e-operator
ci/prow/e2e-agnostic-ipv6 1cedc4b link false /test e2e-agnostic-ipv6
ci/prow/unit 1cedc4b link true /test unit
ci/prow/e2e-console-login 1cedc4b link true /test e2e-console-login
ci/prow/verify-deps 1cedc4b link true /test verify-deps
ci/prow/e2e-agnostic-upgrade 1cedc4b link true /test e2e-agnostic-upgrade
ci/prow/test-operator-integration 1cedc4b link false /test test-operator-integration
ci/prow/verify 1cedc4b link true /test verify

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-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 27, 2025
@openshift-merge-robot
Copy link
Contributor

PR needs rebase.

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
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants