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 1827688: kubvirt redirect vm, vmi and vmtemplates to virtualization page #5295
Bug 1827688: kubvirt redirect vm, vmi and vmtemplates to virtualization page #5295
Conversation
@yaacov: This pull request references Bugzilla bug 1827688, 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. |
@yaacov: This pull request references Bugzilla bug 1827688, 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. |
2 similar comments
@yaacov: This pull request references Bugzilla bug 1827688, 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. |
@yaacov: This pull request references Bugzilla bug 1827688, 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. |
/test e2e-gcp-console |
2 similar comments
/test e2e-gcp-console |
/test e2e-gcp-console |
'/k8s/ns/:ns/virtualmachines', | ||
'/k8s/all-namespaces/virtualmachines', | ||
'/k8s/ns/:ns/virtualmachineinstances', | ||
'/k8s/all-namespaces/virtualmachineinstances', |
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.
IMO we shouldn't overwrite virtualmachineinstances path as it might be useful to have a view just for simple CRDs (eg you just want to drill to the yaml of the VMI once it comes up)
I don't see a big problem of having path for simple VirtualMachine CR too since we are not advertising this path anywhere (just the CRDs page), but I guess we could redirect to virtualization
can we get more opinions on this? @matthewcarleton @jelkosz
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.
We need to override the vanila vm and vmtemplate links because:
a - autogenerated urls use the object type to generate the link, link to vm and vmtemplate lists, if we do not redirect this links, we will send users to the wrong page.
b - the vm and vmtemplate list views do not give the user extra data.
vmi list view different, the list view of vmis show all vims while the virtualization list view show only vmis that are not owned by vms.
@matthewcarleton we need you help with the vmi list hiding issue:
a - is it ok to hide the vanila vmi list, without giving users alternative way to see a list of all vmis ?
b - can we add an option to the vm/vmi list to show only vms or only vmi's in a way that when showing only vmi's we will show all of them including those with vm owners ?
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.
We need to override the vanila vm and vmtemplate links because:
a - autogenerated urls use the object type to generate the link, link to vm and vmtemplate lists, if we do not redirect this links, we will send users to the wrong page.
b - the vm and vmtemplate list views do not give the user extra data.vmi list view different, the list view of vmis show all vims while the virtualization list view show only vmis that are not owned by vms.
@matthewcarleton we need you help with the vmi list hiding issue:
a - is it ok to hide the vanila vmi list, without giving users alternative way to see a list of all vmis ?
b - can we add an option to the vm/vmi list to show only vms or only vmi's in a way that when showing only vmi's we will show all of them including those with vm owners ?
Both of these questions sound like filtering questions. I am reluctant to say we should allow the user to filter the list based on VMI/VM because we'd have to customize the filtering mechanism right? I know that OCP will be delivering a new toolbar which we could make use of then. Do we have use cases where we know this type of capability is needed?
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 am reluctant to say we should allow the user to filter the list based on VMI/VM because we'd have to customize the filtering mechanism right?
it's already customized ... so no problem here :-)
we should open a BZ saying we want to filter by vm vs vmi ...
Do we have use cases where we know this type of capability is needed?
no, just guesses based on what we ( not so avarage users :-) ) think will be nice :-)
/lgtm |
/lgtm cancel |
url parameters shoul be propagated for list sorting:
|
@suomiy redirect now propagate params 🍰 |
/retest |
/retest |
/retest |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest |
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest |
/retest Please review the full test history for this PR and help us cut down flakes. |
4 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest |
/lgtm cancel This change has build errors |
Gentle reminder to look at job failures before retesting.
|
@spadgett Thanks !! fixing |
/test e2e-gcp-console |
4a91906
to
342a821
Compare
342a821
to
487003b
Compare
typing thingy fixed 🍰 |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: irosenzw, suomiy, yaacov 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 |
@yaacov: All pull requests linked via external trackers have merged: openshift/console#5295. Bugzilla bug 1827688 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. |
After changing the Virtualization structure, when a user navigates to
k8s//virtualmachines
There is list of virtual machines, which displays only some VM attributes and does't allow all actions from the kebab menu.
This PR add redirects to virtualization page:
Screenshots:
Dashbord link:
Template breadcrumbs:
Nmaespace change:
Ref:
https://bugzilla.redhat.com/show_bug.cgi?id=1829213
https://bugzilla.redhat.com/show_bug.cgi?id=1827688