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

MGMT-19778: Steps of configuring of Standalone cluster are not progressing #2797

Conversation

jgyselov
Copy link
Collaborator

@jgyselov jgyselov added this to the v2.14-cim milestone Feb 25, 2025
@jgyselov jgyselov requested a review from a team as a code owner February 25, 2025 08:49
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 25, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 25, 2025

@jgyselov: This pull request references MGMT-19778 which is a valid jira issue.

In response to this:

https://issues.redhat.com/browse/MGMT-19778

BP of: #2787

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 size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Feb 25, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 25, 2025

@jgyselov: This pull request references MGMT-19778 which is a valid jira issue.

In response to this:

https://issues.redhat.com/browse/MGMT-19778

BP of: #2787

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.

ammont82
ammont82 previously approved these changes Feb 25, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 25, 2025
@jgyselov jgyselov force-pushed the cim_wizard_rework_2.14 branch from 3e28c48 to 2220241 Compare February 25, 2025 12:01
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 25, 2025
rawagner
rawagner previously approved these changes Feb 25, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 25, 2025
@jgyselov jgyselov force-pushed the cim_wizard_rework_2.14 branch from 2220241 to 1bbdb37 Compare February 25, 2025 13:09
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 25, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 25, 2025
Copy link

openshift-ci bot commented Feb 25, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ammont82, jgyselov

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

@jgyselov jgyselov merged commit a67f5f7 into openshift-assisted:releases/v2.14-cim Feb 26, 2025
7 checks passed
@jgyselov jgyselov deleted the cim_wizard_rework_2.14 branch February 26, 2025 07:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants