Bug 2132793
Summary: | Edited Template BSR is not saved | ||
---|---|---|---|
Product: | Container Native Virtualization (CNV) | Reporter: | Leon Kladnitsky <lkladnit> |
Component: | User Experience | Assignee: | Ugo Palatucci <upalatuc> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Leon Kladnitsky <lkladnit> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 4.12.0 | CC: | cnv-qe-bugs, gouyang, upalatuc |
Target Milestone: | --- | ||
Target Release: | 4.12.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-11-21 02:45:40 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Leon Kladnitsky
2022-10-06 17:44:47 UTC
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. |