Bug 1714937
| Summary: | Disable VXHS support | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux Advanced Virtualization | Reporter: | Miroslav Rezanina <mrezanin> |
| Component: | qemu-kvm | Assignee: | Miroslav Rezanina <mrezanin> |
| Status: | CLOSED ERRATA | QA Contact: | CongLi <coli> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 8.1 | CC: | chayang, coli, ddepaula, jen, juzhang, knoel, michen, mtessun, ngu, qzhang, virt-maint |
| Target Milestone: | rc | Keywords: | Reopened |
| Target Release: | 8.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | qemu-kvm-4.0.0-4.module+el8.1.0+3356+cda7f1ee | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1560447 | Environment: | |
| Last Closed: | 2019-11-06 07:15:20 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1560447 | ||
| Bug Blocks: | 1714933 | ||
|
Comment 2
Miroslav Rezanina
2019-05-29 14:05:58 UTC
Received confirmation from PM that we ended our partnership for VXHS support and we should disable it everywhere. Reopen to post fix cleaning our tree and properly disabling the support. Please grant pm_ack+ as the automatic rules are not working for this (maybe due the reopened keyword?) The patch for this was sent to 8.1.0 (In reply to Danilo Cesar de Paula from comment #6) > Please grant pm_ack+ as the automatic rules are not working for this (maybe > due the reopened keyword?) Apparently you woke up the bot. Fix included in qemu-kvm-4.0.0-4.module+el8.1.0+3356+cda7f1ee Verified on qemu-kvm-4.0.0-4.module+el8.1.0+3356+cda7f1ee.x86_64. # qemu-img info vxhs://8.8.8.8:1002/xx qemu-img: Could not open 'vxhs://8.8.8.8:1002/xx': Unknown protocol 'vxhs' 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:3723 |