Bug 1367293
| Summary: | Incorrect alignment for the stripe size textbox when user selects RAID6 volume in the create brick dialog | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | RamaKasturi <knarra> | ||||||
| Component: | Frontend.WebAdmin | Assignee: | Sahina Bose <sabose> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | SATHEESARAN <sasundar> | ||||||
| Severity: | low | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 4.0.2.4 | CC: | bugs, sabose, sasundar | ||||||
| Target Milestone: | ovirt-4.2.2 | Flags: | sabose:
ovirt-4.2?
rule-engine: planning_ack? rule-engine: devel_ack+ rule-engine: testing_ack+ |
||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | ovirt-engine-4.2.2 | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2018-05-10 06:23:08 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | Gluster | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
RamaKasturi
2016-08-16 06:56:32 UTC
Created attachment 1191113 [details]
Alignment of stripe size
Created attachment 1392007 [details]
createbrick-4.2
Sahina, which version of ovirt-engine contains the code to be tested by QE? I don't see any referenced patch attached to the bug. This is fixed as part of the UI changes in ovirt 4.2 Tested with RHV 4.2.3 This issue is fixed as pointed out by Sahina in comment5 This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.2 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. |