Description of problem: When editing boot source rererence of Template, the changes are not saved Version-Release number of selected component (if applicable): v4.12.0-131 How reproducible: always Steps to Reproduce: 1. Select Template without source, e.g. windows11-desktop-large 2. Select Edit boot source reference from Actions menu 3. Provide boot reference, e.g. Registry/quay.io/containerdisks/centos:7-2009 or URL/http://cnv-qe-server.rhevdev.lab.eng.rdu2.redhat.com/files/cnv-tests/cirros-images/cirros-0.5.1-x86_64-disk.img 4. Save 5. Select Edit boot source reference from Actions menu again Actual results: Changes are not saved Expected results: Changes are saved, Template has "Source available" label in Templates list and Catalog Additional info: related problem in 4.11: https://bugzilla.redhat.com/show_bug.cgi?id=2106179
The bug is fixed, you need to manually move this bug to ON_QA, so it can be verified.
Verified on v4.12.0-147
Regression in KCP v4.12.0-149. The BSR is not saved, "Source available" label is not added to the Template, though the DV for it is created.
DVs are garbage collected in 4.12, let's retest this on a newer CNV version.
After the BSR change, the template list would not update its data. Now the DV and PVC statuses are fetched only at the initial render and the resources are not in a 'watching' state. if the resource change, the user will not have any clue unless change pages and return to the template list. We could put some effort into having a responsive table (from a DV viewpoint) so that when the DV change, the template list will change accordingly. But, when the user changes the BSR, the new data source will be fetched and the DV enter in a 'CloneInProgress' state before the 'Available' state. The DV can remain in a 'CloneInProgress' state before moving to 'Available' for quite some time. So, we'll never have an imminent 'Source available' label when submitting BSR even with a 'watching' state. If we want to give 'feedback' to the user after the BSR submission, we could render a 'cloneInProgress' label. Hope this clarify the situation
We will use the jira card https://issues.redhat.com/browse/CNV-21974 to add label 'CloneInProgress' to template. QE will test the boot source become "Source available" after editing the boot source reference.
@gouyang so, can we close this bug?
Close the bug as the source is available on the latest CNV build.