Skip to content

CONSOLE-4842: merge HCP related scenarios #15662

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

CONSOLE-4842: merge HCP related scenarios #15662

wants to merge 1 commit into from
+22 −0

Conversation

@yanpzhan
Copy link
Contributor

@yanpzhan yanpzhan commented Oct 31, 2025 •
edited
Loading

@yapei or anyone else in console team pls help to take a first review, thanks!

@openshift-ci openshift-ci bot added the kind/cypress Related to Cypress e2e integration testing label Oct 31, 2025
@yanpzhan
Copy link
Contributor Author

yanpzhan commented Nov 3, 2025

Tracked in issue https://issues.redhat.com/browse/CONSOLE-4842

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 5, 2025

@yanpzhan: 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/frontend cd6c0b1 link true /test frontend
ci/prow/okd-scos-e2e-aws-ovn cd6c0b1 link false /test okd-scos-e2e-aws-ovn

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.

@yapei
Copy link
Contributor

yapei commented Nov 6, 2025

we also need update title to include user story identifier

CONSOLE-4842: merge HCP related scenarios

@jhadvig jhadvig changed the title merge HCP related scenarios to upstream CONSOLE-4842: merge HCP related scenarios Nov 6, 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 Nov 6, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Nov 6, 2025 •
edited by openshift-ci bot
Loading

@yanpzhan: This pull request references CONSOLE-4842 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 sub-task to target the "4.21.0" version, but no target version was set.

In response to this:

@yapei or anyone else in console team pls help to take a first review, thanks!

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.

@jhadvig
Copy link
Member

jhadvig commented Nov 6, 2025

@yanpzhan for the record you can use the /retitle ... cmd ;)

jhadvig
jhadvig approved these changes Nov 6, 2025
View reviewed changes
Copy link
Member

@jhadvig jhadvig left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

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

openshift-ci bot commented Nov 6, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jhadvig, yanpzhan

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 Nov 6, 2025
@jhadvig jhadvig added docs-approved Signifies that Docs has signed off on this PR px-approved Signifies that Product Support has signed off on this PR labels Nov 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jhadvig jhadvig jhadvig approved these changes

@krishagarwal278 krishagarwal278 Awaiting requested review from krishagarwal278

@sg00dwin sg00dwin Awaiting requested review from sg00dwin

+1 more reviewer

@yapei yapei yapei left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

@jhadvig jhadvig

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. docs-approved Signifies that Docs has signed off on this PR jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. kind/cypress Related to Cypress e2e integration testing lgtm Indicates that a PR is ready to be merged. px-approved Signifies that Product Support has signed off on this PR

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@yanpzhan @yapei @openshift-ci-robot @jhadvig