Bug 1817394
Summary: | Added CD ROMs in UI other than Windows Guest Disk use VirtIO instead of sata | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Tomas Jelinek <tjelinek> |
Component: | Console Kubevirt Plugin | Assignee: | Gilad Lekner <glekner> |
Status: | CLOSED ERRATA | QA Contact: | Radim Hrazdil <rhrazdil> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.4 | CC: | aburden, aos-bugs, gouyang, irosenzw, ncredi, rhrazdil, xiuwang, yzamir |
Target Milestone: | --- | ||
Target Release: | 4.4.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Known Issue | |
Doc Text: |
Cause:
The default cdrom interface in vm wizard is "virtio" while the backend does not allow vm with virtio cdroms to be created.
Consequence:
If the user decides to attach a new CDRom in the wizard and leaves the interface on the default value, validation will not let this vm to be created. Consequently, the user always needs to change the interface to sata manually.
Workaround (if any):
If the user wants to add a cdrom from the wizard, he always needs to pick the interface to be sata instead of virtio.
Result:
With this workaround the vm successfully creates.
|
Story Points: | --- |
Clone Of: | 1813198 | Environment: | |
Last Closed: | 2020-06-23 00:57:24 UTC | Type: | --- |
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: | 1813198 | ||
Bug Blocks: |
Comment 1
Andrew Burden
2020-04-29 11:03:10 UTC
submitted upsream: https://github.com/openshift/console/pull/5496 tested on upstream 4.4 branch with commit ef3268ae549554e51b2a96b8a9771553e23901dd the default interface of disk is "sata", the bug is fixed. @Guohua Could you help to update the bug status? 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-2020:2580 |