Component version is always the same about cockpit-composer

[jgiardino]

I'd like to be able to test this UI against a dataset that has multiple versions available for a component.

@andreasn @larskarlitski Do you have any suggestions on how to get a dataset I can use?

My assumption is that the user could have a mix of components, where some have several options and some have only one. For that scenario, and in the case where only one option is available, do you think displaying the value as read-only is the right thing to do? I question if that's more confusing than a select menu with just one option, but we can also always do user testing to confirm.

[KKoukiou]

This is indeed reproducible.

For example on my system I have libvirt package provided by two different repositories, and the versions in these are different. See bellow:

# dnf list libvirt 
Last metadata expiration check: 0:05:28 ago on Thu 25 Apr 2019 03:05:08 PM CEST.
Installed Packages
libvirt.x86_64                                                         5.1.0-4.fc30                                                          @updates-testing                
Available Packages
libvirt.src                                                            5.2.0-2.fc30                                                          group_virtmaint-sig-virt-preview
libvirt.x86_64                                                         5.2.0-2.fc30                                                          group_virtmaint-sig-virt-preview

However lorax allow me to install only 5.2.0?

I didn't looks at the code yet, but from user perspective, is that expected? @larskarlitski

[jkozol]

Closed as out of date