Bug 1908650
| Summary: | The title of customize wizard is inconsistent | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Guohua Ouyang <gouyang> | ||||||||||
| Component: | Console Kubevirt Plugin | Assignee: | Gilad Lekner <glekner> | ||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Guohua Ouyang <gouyang> | ||||||||||
| Severity: | medium | Docs Contact: | |||||||||||
| Priority: | medium | ||||||||||||
| Version: | 4.7 | CC: | aos-bugs, glekner, gouyang, mcarleto, yzamir | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | 4.7.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: | 2021-02-24 15:46:22 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: |
|
||||||||||||
|
Description
Guohua Ouyang
2020-12-17 09:22:58 UTC
I'm seeing "Create Virtual Machine" Alone in both cases. can you make sure the reproducing steps work? Thanks Ah, it seems only happen when the template is created by user, such as create a template from yaml and use it to create the VM, then the title is "Create Virtual Machine from vm-template-example". Gilad, Guohua hi, IMHO in the new flow where common-templates are used the same way as user-templates, we should show the "from template ..." in both cases, WDYT ? (In reply to Yaacov Zamir from comment #3) > Gilad, Guohua hi, IMHO in the new flow where common-templates are used the > same way as user-templates, we should show the "from template ..." in both > cases, WDYT ? I have no problem with this. What about when the template has no source available, it's "Create Virtual Machine", looks like we don't consider it's creating from a template through we select a template at the first step. Hey @mcarleto can you please give your input here In this scenario, they are creating a VM from a template with a custom boot source right? If that's true we should still say Which template they are creating from but clarify they are adding a custom boot source. Create virtual machine from template-x with custom boot source" WDYT? Matt Gilad hi, currently after a user selects a template, and choose "customize this VM", in the old wizard (the complicated one with 6 tabs) we show the title: for templates provided by community / user : we show "create VM from template <user template name>" for templates provided by redhat : we show "create VM" [ this bug doesn't exist in the new wizard where we have help text that expose the template name the same way for community and redhat provided templates ] the bug is why the old wizard hide the template name in the case of redhat provided common-templates ? @Matt, the question is: Do we hide the template name in the old wizard by design, or is it a bug and we should show the template name in a simmilar way to the way we do in the new wizard ? Created attachment 1744492 [details]
new wizard create from common template
Created attachment 1744493 [details]
old wizard create from common-template
Created attachment 1744494 [details]
new wizard create from user template
Created attachment 1744495 [details]
old wizard create from user template
we should always show the name of the template they are creating from, yes. 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement 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-2020:5633 |