Bug 2176746
| Summary: | Not able to distinguish templates in catalog list view | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Container Native Virtualization (CNV) | Reporter: | Guohua Ouyang <gouyang> | ||||||||||
| Component: | User Experience | Assignee: | Aviv Turgeman <aturgema> | ||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Guohua Ouyang <gouyang> | ||||||||||
| Severity: | medium | Docs Contact: | |||||||||||
| Priority: | medium | ||||||||||||
| Version: | 4.13.0 | CC: | fkargbo, gouyang, rsdeor, sjess, upalatuc, ycui, yfrimanm | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | 4.14.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: | 2023-11-08 14:05:04 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: | |||||||||||||
| Attachments: |
|
||||||||||||
Created attachment 1951823 [details]
A diagram for Option 1
I've reviewed this bug and I'm suggesting one of two options: Option 1 We should automatically generate a unique clone name with each new clone created E.g. CentOS 7 VM - Clone 1 >> A diagram for reference is attached. << Option 2 We should make the "Template display name" input field required with inline validation. The inline validation text should alert users to use "unique" names for new clones. The inline validation text is "Specify a unique name" >> A diagram for reference is attached. << Created attachment 1951824 [details]
A diagram for Option 2
We can combine option #1 and #2 together as a fix. Should we allow display names of templates in different namespaces? @gouyang (In reply to Ugo Palatucci from comment #5) > Should we allow display names of templates in different namespaces? Yes, when "All projects" are selected in "Template project". @gouyang do you like this text for the modal 'This display name is already used in another template of the same namespace.' ? @sjess please review the text @upalatuc suggested in comment #8. Thanks. Looking at the UI, it's clear it's an error message and that the error message is for the Template display name, so I think you can keep it as short as "Name already in use." If you want to add more, maybe "Name already in use. Choose a unique name." but that feels a bit redundant. Verified, now a label is added next to it to make them look different. Created attachment 1959484 [details]
Distinguish between templates
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 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |
Created attachment 1949215 [details] not able to tell the difference between templates Description of problem: Clone some templates and then visit catalog -> template list view, it looks not able to distinguish templates from there. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: