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

fix: added Rack info for the topology details screen #946

Merged

Conversation

debjyoti-pandit
Copy link
Contributor

@debjyoti-pandit debjyoti-pandit commented Aug 1, 2023

fixes: https://bugzilla.redhat.com/show_bug.cgi?id=2214023

when only zone is present
image

when only rack is present
image

just in case we have both of them
image

@debjyoti-pandit debjyoti-pandit changed the title fix: added Rack info for the topology details screen Bug 2214023: added Rack info for the topology details screen Aug 1, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 1, 2023

@debjyoti-pandit: This pull request references Bugzilla bug 2214023, which is valid.

No validations were run on this bug

No GitHub users were found matching the public email listed for the QA contact in Bugzilla ([email protected]), skipping review request.

In response to this:

Bug 2214023: added Rack info for the topology details screen

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/test-infra repository.

@debjyoti-pandit
Copy link
Contributor Author

/assign @bipuladh
/assign @SanjalKatiyar

@SanjalKatiyar
Copy link
Collaborator

LGTM (but we are now maintaining RACK_LABEL and getRack at 2 diff packages, should be always under shared and be removed from other place)

@debjyoti-pandit
Copy link
Contributor Author

LGTM (but we are now maintaining RACK_LABEL and getRack at 2 diff packages, should be always under shared and be removed from other place)

True, should I refactor it in this PR itself only?

@SanjalKatiyar
Copy link
Collaborator

LGTM (but we are now maintaining RACK_LABEL and getRack at 2 diff packages, should be always under shared and be removed from other place)

True, should I refactor it in this PR itself only?

yup...

@SanjalKatiyar
Copy link
Collaborator

plz fix the build tests...

@SanjalKatiyar
Copy link
Collaborator

update the PR title correctly as per the guidelines...

@debjyoti-pandit debjyoti-pandit changed the title Bug 2214023: added Rack info for the topology details screen Fix: added Rack info for the topology details screen Aug 9, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 9, 2023

@debjyoti-pandit: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

Fix: added Rack info for the topology details screen

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/test-infra repository.

@debjyoti-pandit debjyoti-pandit changed the title Fix: added Rack info for the topology details screen fix: added Rack info for the topology details screen Aug 9, 2023
@debjyoti-pandit
Copy link
Contributor Author

/test odf-console-e2e-aws

@SanjalKatiyar
Copy link
Collaborator

squash the commits...

@SanjalKatiyar
Copy link
Collaborator

/test odf-console-e2e-aws

@SanjalKatiyar
Copy link
Collaborator

/cherry-pick release-4.14-compatibility

@openshift-cherrypick-robot

@SanjalKatiyar: once the present PR merges, I will cherry-pick it on top of release-4.14-compatibility in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.14-compatibility

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/test-infra repository.

@SanjalKatiyar
Copy link
Collaborator

/cherry-pick release-4.14

@openshift-cherrypick-robot

@SanjalKatiyar: once the present PR merges, I will cherry-pick it on top of release-4.14 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.14

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/test-infra repository.

@SanjalKatiyar
Copy link
Collaborator

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm label Aug 14, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 14, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: debjyoti-pandit, SanjalKatiyar

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-merge-robot openshift-merge-robot merged commit 7a07e8e into red-hat-storage:master Aug 14, 2023
3 checks passed
@openshift-cherrypick-robot

@SanjalKatiyar: new pull request created: #968

In response to this:

/cherry-pick release-4.14-compatibility

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/test-infra repository.

@openshift-cherrypick-robot

@SanjalKatiyar: new pull request created: #969

In response to this:

/cherry-pick release-4.14

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/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants