Bug 1647025
Summary: | [downstream clone - 4.2.8] RESTAPI listing diskprofiles only shows 1 href for the same QoS even if there are more domains with the same QoS | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | RHV bug bot <rhv-bugzilla-bot> |
Component: | ovirt-engine | Assignee: | shani <sleviim> |
Status: | CLOSED ERRATA | QA Contact: | Evelina Shames <eshames> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.2.5 | CC: | dfodor, ebenahar, eedri, ratamir, rbarry, Rhev-m-bugs, sborella, tnisan |
Target Milestone: | ovirt-4.2.8 | Keywords: | ZStream |
Target Release: | --- | Flags: | lsvaty:
testing_plan_complete-
|
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | ovirt-engine-4.2.8.1 | Doc Type: | Bug Fix |
Doc Text: |
This fix addresses listing disk profiles on a storage domain that have a Quality of Service link set where the href attribute value for the QoS link does not display for each listing. This release ensures that all QoS link values are visible.
|
Story Points: | --- |
Clone Of: | 1640977 | Environment: | |
Last Closed: | 2019-01-22 12:44:50 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: | |||
Bug Depends On: | 1640977 | ||
Bug Blocks: |
Description
RHV bug bot
2018-11-06 14:36:18 UTC
WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Found non-acked flags: '{'rhevm-4.2.z': '?'}', ] For more info please contact: rhv-devops: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Found non-acked flags: '{'rhevm-4.2.z': '?'}', ] For more info please contact: rhv-devops This bug should have been moved to ON_QA I can see it only got 4.2.z+ today, so it should move to ON_QA once the compose is done and new build is released TODAY. @Dusan, please have a look at it once you do the release to verify. Verified on engine 4.2.8.1-0.1 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/RHBA-2019:0121 sync2jira sync2jira |