-
Notifications
You must be signed in to change notification settings - Fork 667
Bug 2006308: Backing Store YAML tab on click displays a blank screen on UI #10119
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 2006308: Backing Store YAML tab on click displays a blank screen on UI #10119
Conversation
|
@SanjalKatiyar: This pull request references Bugzilla bug 2006308, 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
No GitHub users were found matching the public email listed for the QA contact in Bugzilla (ratamir@redhat.com), skipping review request. DetailsIn 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. |
| "path": "/odf/resource/noobaa.io~v1alpha1~BucketClass/create/~new", | ||
| "exact": true, | ||
| "path": "/odf/resource/:resourceKind/:resourceName", | ||
| "exact": false, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just making this one change. Should be enough right? Why are we changing the order of the extension declaration?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think, it will affect.
This BZ will work fine even if we do not change the order. But, it will create a new bug instead.
Let's suppose I clicked on the "Create Backing Store" button on the list page. It will check all the available Routes. If this Route (with exact = false) is defined before the Route for creating backing-store component then this Route will be matched (because we are using exact = false here) and it will not load create-backing-store specific component.
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bipuladh, SanjalKatiyar The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
4 similar comments
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
@SanjalKatiyar: All pull requests linked via external trackers have merged: Bugzilla bug 2006308 has been moved to the MODIFIED state. DetailsIn 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. |
|
/cherry-pick release-4.9 |
|
@bipuladh: new pull request created: #10603 DetailsIn 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. |
Routing issue with
Backing StoreBucket ClassNameSpace Store.Backing Store --> backing-store details --> YAML Tab
Before:

After:
