Description of problem: Currently, the boot order items are all in plain text, no difference between them. Maybe it can have some icon to make them look different. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Guohua, can you, please, provide more details about this bug? Did you mean "Boot order" field displayed in the VM Details tab or something else? Yifat, what do you think about this issue? Is that ever an issue? Do we need to distinguish between disks and network in there? If yes, then how? Thanks in advance!
(In reply to Hilda Stastna from comment #1) > Guohua, can you, please, provide more details about this bug? Did you mean > "Boot order" field displayed in the VM Details tab or something else? Yes, I mean the "Boot order" field displayed in the VM Details tab. > Yifat, what do you think about this issue? Is that ever an issue? Do we need > to distinguish between disks and network in there? If yes, then how? We should have a UX design for this, as it's not clear enough to both developer and QE. > > Thanks in advance!
@gouyang would you please attach a screenshot? Thank you.
Created attachment 1947343 [details] boot_order_in_details
Created attachment 1947344 [details] boot order in add list
If we add the distinguishes to the boot orders, maybe we should add it to all place which has the boot item list
@gouyang regarding attachment 1947344 [details] https://bugzilla.redhat.com/attachment.cgi?id=1947344 TMO the "remove" icon should not be shown next to the dropdown. It should only appear next to a bootsource item to enable deleting it.
(In reply to Guohua Ouyang from comment #6) > If we add the distinguishes to the boot orders, maybe we should add it to > all place which has the boot item list +1
I have a pr to completely remove the 'add' dropdown. If I'm understanding correctly, all devices, in theory, are bootable. We should show all the devices and the user should be able to just give an order. Removing the device from that list as it is now, just remove the bootOrder property. But removing that property doesn't mean that the device is not bootable. It's still bootable but not having that property gives just a lower priority. https://github.com/kubevirt-ui/kubevirt-plugin/pull/1167.
@gouyang
(In reply to Ugo Palatucci from comment #9) > I have a pr to completely remove the 'add' dropdown. It looks good to me and the bug 2174619 is verified. > If I'm understanding correctly, all devices, in theory, are bootable. We > should show all the devices and the user should be able to just give an > order. > Removing the device from that list as it is now, just remove the bootOrder > property. But removing that property doesn't mean that the device is not > bootable. > > It's still bootable but not having that property gives just a lower > priority. https://github.com/kubevirt-ui/kubevirt-plugin/pull/1167.
@yfrimanm hei Yifat. So is there something we can do to enhance the user experience on this modal? Some icons to differentiate the two types of devices?
Created attachment 1953962 [details] Boot order modal w- icons to differentiate between disks and network @upalatuc please see the Boot Order icons modal. Thanks.
verified on kubevirt-console-plugin-rhel9-container-v4.14.0-1047
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Virtualization 4.14.0 Images security and bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2023:6817