Bug 1572158
| Summary: | [RFE] add disk sizes in Disk general tab | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Roman Hodain <rhodain> | ||||||||||
| Component: | Frontend.WebAdmin | Assignee: | Eyal Shenitzky <eshenitz> | ||||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Natalie Gavrielov <ngavrilo> | ||||||||||
| Severity: | medium | Docs Contact: | |||||||||||
| Priority: | high | ||||||||||||
| Version: | 4.2.2.6 | CC: | bugs, eshenitz, gshereme, jbryant, ngavrilo, pstehlik, ratamir, rhodain, tjelinek, tnisan, ylavi | ||||||||||
| Target Milestone: | ovirt-4.2.5 | Keywords: | FutureFeature | ||||||||||
| Target Release: | --- | Flags: | rule-engine:
ovirt-4.2+
ylavi: planning_ack+ rule-engine: devel_ack+ ebenahar: testing_ack+ |
||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Enhancement | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | 1572155 | Environment: | |||||||||||
| Last Closed: | 2018-07-31 15:25:19 UTC | Type: | Bug | ||||||||||
| 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
Roman Hodain
2018-04-26 09:48:08 UTC
Did it show it in 4.1? Created attachment 1450351 [details]
Situation in 4.1
There were not all the information, but there was at least the information about the virtual size. It is not perfect but now when you click on a disk in 4.2 the list disappears and you cannot see even the virtual size.
Need to backport, return to POST (In reply to Roman Hodain from comment #2) > Created attachment 1450351 [details] > Situation in 4.1 > > There were not all the information, but there was at least the information > about the virtual size. It is not perfect but now when you click on a disk > in 4.2 the list disappears and you cannot see even the virtual size. This means it's a regression from 4.1, we want it for 4.2.4 then Created attachment 1452656 [details]
Screenshot from disks general tab
With the latest build - 4.2.4.1-0.1.el7, the disks general tab doesn't include actual size, neither the 'images' tag view. Is the intentional?
(In reply to Shir Fishbain from comment #5) > Created attachment 1452656 [details] > Screenshot from disks general tab > > With the latest build - 4.2.4.1-0.1.el7, the disks general tab doesn't > include actual size, neither the 'images' tag view. Is the intentional? Select a disk and check the general tab it should appear there (In reply to Shir Fishbain from comment #5) > Created attachment 1452656 [details] > Screenshot from disks general tab > > With the latest build - 4.2.4.1-0.1.el7, the disks general tab doesn't > include actual size, neither the 'images' tag view. Is the intentional? Select a disk and check the general tab it should appear there Created attachment 1454291 [details]
snapshot
Actual size is displayed now - which is good but..
Wipe After Delete seems to be displaying the Virtual size value (instead of Yes/No) and Virtual size shows nothing.
Build:
rhvm-4.2.4.5-0.1.el7_3.noarch
Created attachment 1455236 [details]
actual virtual sizes UI - master branch
This is strange, It seems to display properly on the master branch. I've added a screenshot. Natalie, can you please supply more details on the disk you created? is there something specific? Which browser did you use to test it? Verified using 4.2.5.1_SNAPSHOT-73.g63529de.0.scratch.master.el7ev Now all fields look fine (Wipe After Delete, Virtual Size, Actual Size) *** Bug 1601574 has been marked as a duplicate of this bug. *** This bugzilla is included in oVirt 4.2.5 release, published on July 30th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.5 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |