Bug 1429482
| Summary: | Difference between VV file content and data received as a response for REST api call to get VV file content. | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Vitalii Yerys <vyerys> |
| Component: | BLL.Virt | Assignee: | Tomasz BaraĆski <tbaransk> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Liran Rotenberg <lrotenbe> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.1.1 | CC: | bugs, rbarry, tjelinek |
| Target Milestone: | ovirt-4.3.1 | Flags: | tjelinek:
ovirt-4.3?
tjelinek: planning_ack? rule-engine: devel_ack+ rule-engine: testing_ack+ |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-engine-4.3.1.1 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-03-01 10:20:21 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Vitalii Yerys
2017-03-06 13:11:01 UTC
AFAIK there was a difference also in the USB filter field (e.g. missing from API) unfortunately have to postpone it due to capacity Re-targeting to 4.3.1 since it is missing a patch, an acked blocker flag, or both Verified on: ovirt-engine-4.3.0.5-0.0.master.20190210112640.git53b60e3.el7.noarch Steps: 1. Create VM with spice console protocol used and start it. 2. Download VV file via UI. 3. Verify field "title" is present in the VV file. 4. Download VV file info via REST, using following call: NOTE: use 'Accept': 'application/x-virt-viewer' header. GET ../ovirt-engine/api/vms/<vm-id>/graphicsconsoles/<console-id> Results: Raw response body does contain "title" field, matching value from UI and REST API. This bugzilla is included in oVirt 4.3.1 release, published on February 28th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.1 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. |