Bug 1445276
| Summary: | ovirt 4.1 rest api is sending unexpected results | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Radek Duda <rduda> |
| Component: | mingw-virt-viewer | Assignee: | Default Assignee for SPICE Bugs <rh-spice-bugs> |
| Status: | CLOSED ERRATA | QA Contact: | SPICE QE bug list <spice-qe-bugs> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.1.0 | CC: | apinnick, astepano, cfergeau, dblechte, elima, lsurette, rbalakri, rduda, rh-spice-bugs, spice-qe-bugs, srevivo, tpelka, victortoso |
| Target Milestone: | ovirt-4.2.1 | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | mingw-virt-viewer-2.0-15.el7ev mingw-libgovirt-0.3.4-3.el7ev | Doc Type: | No Doc Update |
| Doc Text: |
undefined
|
Story Points: | --- |
| Clone Of: | 1411325 | Environment: | |
| Last Closed: | 2018-05-15 18:02:00 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Spice | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1411325 | ||
| Bug Blocks: | |||
|
Comment 1
Eduardo Lima (Etrunko)
2017-10-18 15:11:04 UTC
Requesting this to 4.2 as the fix is upstream already (In reply to Victor Toso from comment #2) > Requesting this to 4.2 as the fix is upstream already but 4.2.0 has already been built. (In reply to Yaniv Kaul from comment #3) > (In reply to Victor Toso from comment #2) > > Requesting this to 4.2 as the fix is upstream already > > but 4.2.0 has already been built. Are we still in the testing phase? Yes, according to the 4.2 schedule. So, why it is a problem to fix the issues that are filed by QE during testing phase? If we are not allowed, than the bot should be fixed first, as it granted the PM_ACK automatically. Fixing virt-viewer version that this bug should really be fixed. Previous build did not pick the correct dependencies with the backported patches. 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-2018:1543 BZ<2>Jira Resync |