Bug 1797927
| Summary: | [REST-API] Attaching/adding a disk with SATA interface to a VM fails with Exception Caused by: java.lang.IllegalArgumentException: Unknown disk interface "SATA" | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Avihai <aefrat> | ||||
| Component: | BLL.Virt | Assignee: | Liran Rotenberg <lrotenbe> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Polina <pagranat> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.4.0 | CC: | bpelled, bugs, eshenitz, lrotenbe, rbarry, tnisan | ||||
| Target Milestone: | ovirt-4.4.0 | Flags: | pm-rhel:
ovirt-4.4+
|
||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | rhv-4.4.0-29 | Doc Type: | No Doc Update | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-05-20 20:01:24 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: | |||||||
| Attachments: |
|
||||||
|
Description
Avihai
2020-02-04 08:59:37 UTC
this bug is in modified and targeting 4.4.2. Can we re-target to 4.4.0 and move to QE? verified on http://bob-dr.lab.eng.brq.redhat.com/builds/4.4/rhv-4.4.0-31. test1(with iscsi storage domain): POST https://{{host}}/ovirt-engine/api/vms/f2bad84d-722a-49c4-8c0f-082526d21372/diskattachments <disk_attachment> <bootable>false</bootable> <pass_discard>false</pass_discard> <interface>sata</interface> <active>true</active> <disk> <provisioned_size>1073741824</provisioned_size> <format>cow</format> <storage_domains> <storage_domain> <name>iscsi_0</name> </storage_domain> </storage_domains> </disk> </disk_attachment> Response 201 <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <disk_attachment href="/ovirt-engine/api/vms/f2bad84d-722a-49c4-8c0f-082526d21372/diskattachments/2daa0c4b-865a-44a0-81ef-afd427f3e6a8" id="2daa0c4b-865a-44a0-81ef-afd427f3e6a8"> <active>true</active> <bootable>false</bootable> <interface>sata</interface> <pass_discard>false</pass_discard> <read_only>false</read_only> <uses_scsi_reservation>false</uses_scsi_reservation> <disk href="/ovirt-engine/api/disks/2daa0c4b-865a-44a0-81ef-afd427f3e6a8" id="2daa0c4b-865a-44a0-81ef-afd427f3e6a8"/> <vm href="/ovirt-engine/api/vms/f2bad84d-722a-49c4-8c0f-082526d21372" id="f2bad84d-722a-49c4-8c0f-082526d21372"/> </disk_attachment> test2 (with nfs storage domain): POST https://{{host}}/ovirt-engine/api/vms/171081fd-415e-4636-8fe1-37b19bf2b749/diskattachments <disk_attachment> <bootable>false</bootable> <pass_discard>false</pass_discard> <interface>sata</interface> <active>true</active> <disk> <provisioned_size>1073741824</provisioned_size> <format>cow</format> <storage_domains> <storage_domain> <name>nfs_0</name> </storage_domain> </storage_domains> </disk> </disk_attachment> Responce 201: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <disk_attachment href="/ovirt-engine/api/vms/171081fd-415e-4636-8fe1-37b19bf2b749/diskattachments/3c9a28ac-9dcf-42ae-a784-de40c77a1747" id="3c9a28ac-9dcf-42ae-a784-de40c77a1747"> <active>true</active> <bootable>false</bootable> <interface>sata</interface> <pass_discard>false</pass_discard> <read_only>false</read_only> <uses_scsi_reservation>false</uses_scsi_reservation> <disk href="/ovirt-engine/api/disks/3c9a28ac-9dcf-42ae-a784-de40c77a1747" id="3c9a28ac-9dcf-42ae-a784-de40c77a1747"/> <vm href="/ovirt-engine/api/vms/171081fd-415e-4636-8fe1-37b19bf2b749" id="171081fd-415e-4636-8fe1-37b19bf2b749"/> </disk_attachment> This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.0 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. |