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
Bug 1889724: When LocalVolumeDiscovery CR is created form the LSO page , user must see the Disk tab #6986
Bug 1889724: When LocalVolumeDiscovery CR is created form the LSO page , user must see the Disk tab #6986
Conversation
afreen23
commented
Oct 22, 2020
•
edited
edited
- The flag is set only by OCS and gets undefined when OCS is not installed. The flag must be set by LSO plugin and imported in OCS.
- Created an action flag in LSO package to be set
- Looking for discovery CR rather than discoveryresult CR
- minor fix for empty state too
@afreen23: This pull request references Bugzilla bug 188972, which is invalid:
Comment 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 kubernetes/test-infra repository. |
@afreen23: This pull request references Bugzilla bug 188972, which is invalid:
Comment 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 kubernetes/test-infra repository. |
@afreen23: This pull request references Bugzilla bug 1889724, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
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 kubernetes/test-infra repository. |
e6a4614
to
9eb2da1
Compare
d3d8b9b
to
e1eb102
Compare
Please attach screenshots of the fix. |
@afreen23: This pull request references Bugzilla bug 1889724, which is valid. 3 validation(s) were run on this bug
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 kubernetes/test-infra repository. |
e1eb102
to
d46cb8b
Compare
- created an action flag in LSO package to be set - looking for discovery CR rather than discoveryresult CR - fixed empty state too Signed-off-by: Afreen Rahman <afrahman@redhat.com>
d46cb8b
to
abfe443
Compare
@afreen23: This pull request references Bugzilla bug 1889724, which is valid. 3 validation(s) were run on this bug
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 kubernetes/test-infra repository. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: afreen23, bipuladh 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 |
@afreen23: All pull requests linked via external trackers have merged: Bugzilla bug 1889724 has been moved to the MODIFIED state. 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 kubernetes/test-infra repository. |
/cherrypick release-4.6 |
@afreen23: #6986 failed to apply on top of branch "release-4.6":
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 kubernetes/test-infra repository. |