Bug 1716367
| Summary: | [downstream clone - 4.3.5] [UI] add a tooltip to explain the supported matrix for the combination of disk allocation policies, formats and the combination result | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | RHV bug bot <rhv-bugzilla-bot> | ||||
| Component: | ovirt-engine | Assignee: | Eyal Shenitzky <eshenitz> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Avihai <aefrat> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.2.5 | CC: | aefrat, eshenitz, frolland, lsurette, lwright, michal.skrivanek, Rhev-m-bugs, srevivo, tburke, tnisan | ||||
| Target Milestone: | ovirt-4.3.5 | Keywords: | ZStream | ||||
| Target Release: | 4.3.5 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | ovirt-engine-4.3.5 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | 1616451 | Environment: | |||||
| Last Closed: | 2019-08-12 11:53:28 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
RHV bug bot
2019-06-03 10:34:03 UTC
8 believe this should also be Storage. Not sure if the mapping of raw/qcow to thin/preallocated is exactly like that (Originally by michal.skrivanek) This bug has not been marked as blocker for oVirt 4.3.0. Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1. (Originally by Sandro Bonazzola) Decided to change this bug to add a tooltip to explain the engine volume type / format matrix and the combination results After bug 1573413 will be solved. (Originally by Eyal Shenitzky) Do you guys need any UX help with this bug? I would be happy to write the text for the tooltip. (Originally by Laura Wright) Do you guys need help with 1573413 before we work on this issue? (Originally by Laura Wright) This bug depends on bug 1616451 which depends on bug 1573413(which is in 'NEW' state). Only when all dependent bugs will be also 'ON_QA' we can verify this bug. I think 1616451 is a 4.4 clone this bug does not depend on it, please check it out. However, bug 1573413 describes a new functionality(selecting disk allocation policy when creating a template from a VM) which is not currently available as this bug is in NEW state . Can you check/clarify if this bug really depends on any other bug ? If this bug indeed depends on another bug to be fixed we are showing in the UI a behavior which does not exist and need to revert this fix. remove bug 1573413 dependency. bug 1616451 is the 'upstream' bug. (In reply to Eyal Shenitzky from comment #12) > remove bug 1573413 dependency. So in upstream bug 1616451 you are dependant on bug 1573413(meaning you can also choose allocation policy) and here at the DS bug you are not. This does not look consistent( I would expect upstream/DS bugs to be resolved at the same manner), are you sure this is OK? > bug 1616451 is the 'upstream' bug Correct, but why it is blocking(marked here as 'depends on' this downstream bug? If bug A(upstream) is blocking bug B(downstream) I cannot verify bugB(DS) until bug A(US) is fixed/verified. Also, verification of this issue is not as initial description as Marina wanted to map THIN-Provisioned when talking about qcow2 and Preallocated when talking about RAW -> THIS SHOULD BE CLEAR. Verification is as written in patch https://gerrit.ovirt.org/#/c/100413/ : " Add a new tooltip to: New Virtual Machine-> Resource Allocation-> Storage Allocation to explain the supported disk format/type matrix. screenshot - https://imgur.com/a/BBA4QL2 " right ? Yes, as described in the patch and as seen in the screenshot. Verified at 4.3.5.3-0.1.el7 Created attachment 1588046 [details]
Verification 4.3.5-3 print screen
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, 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/RHEA-2019:2431 |