Hi Marcin, Following the link you've provided earlier [1], it seems to me that your SDK syntax fits the template supplied there in the example. <disk_attachment> <bootable>false</bootable> <interface>virtio</interface> <active>true</active> <disk id="a016b350-87ef-4c3b-b150-024907fed9c0"/> </disk_attachment> It also mentioned there that adding an attachment is a POST method: POST /ovirt-engine/api/vms/345/diskattachments In case you attend to update a disk attachment (which already has been attached to the VM), the request should be PUT /vms/{vm:id}/disksattachments/{attachment:id} Hope it helps :) [1] https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/htm... [2] https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/htm... *Regards,* *Shani Leviim* On Wed, Apr 25, 2018 at 3:19 PM, Marcin Kubacki <m.kubacki@storware.eu> wrote:
Hi Shani,
we’re using ovirt SDK for Java, can you please give more details about how that can be achieved using SDK?
Pozdrawiam / Best Regards
Marcin Kubacki Chief Software Architect
e-mail: m.kubacki@storware.eu <j.sobieszczanski@storware.eu> mobile: +48 730-602-612
*ul. Leszno 8/44* *01-192 Warszawa * *www.storware.eu <https://www.storware.eu/>*
Wiadomość napisana przez Shani Leviim <sleviim@redhat.com> w dniu 25.04.2018, o godz. 14:17:
Hi,
Attaching a disk to a VM is a 'POST' method (rather than 'PUT' method). Can you give it a try?
*Regards, *
*Shani Leviim *
On Wed, Apr 25, 2018 at 2:55 PM, Maor Lipchuk <mlipchuk@redhat.com> wrote:
Hi Marcin and Hanna,
I've found the following bug https://bugzilla.redhat.com/1546832 which probably fix that issue, The fix was introduced in oVirt 4.2.3.2 Which version are you using?
Regards, Maor
On Wed, Apr 25, 2018 at 11:24 AM, Maor Lipchuk <mlipchuk@redhat.com> wrote:
Hi Marcin,
Can you please also attach the VDSM log so we can see the exact XML that is being sent to libvirt. (I'm replying on the users list, let's continue to discuss it here)
Regards, Maor
On Tue, Apr 24, 2018 at 5:20 PM, Marcin Kubacki <m.kubacki@storware.eu> wrote:
Hi Maor,
it looks like the problem is deeper, potentially related to how the VM storage is configured (not to the request itself), and it is the first time we’ve seen something like this. Customer has oVirt 4.2, and this wasn’t happening in older environments.
Can you help us solving this issue?
Pozdrawiam / Best Regards
Marcin Kubacki Chief Software Architect
e-mail: m.kubacki@storware.eu <j.sobieszczanski@storware.eu> mobile: +48 730-602-612
*ul. Leszno 8/44* *01-192 Warszawa * *www.storware.eu <https://www.storware.eu/>*
Wiadomość napisana przez Hanna Terentieva <h.terentieva@storware.eu> w dniu 23.04.2018, o godz. 10:33:
Hi Maor,
My request looks correct and as for ovirt mailing list there seems to be a similar issue with VDSM failure here https://www.mail-archive.com/users@ovirt.org/msg45797.html. Have you possibly encountered a similar issue?
On Sun, 2018-04-22 at 10:47 +0300, Maor Lipchuk wrote:
Hi Hanna,
If the diskalready exists you should use PUT method with the following URL: PUT /vms/{vm:id}/disksattachments/{attachment:id}
You can take a look at the following documentation for more details: https://access.redhat.com/documentation/en-us/red_hat_virtua lization/4.1/html-single/rest_api_guide/#services-disk_attac hment-methods-update
If you already done this and still have a problem, I suggest to send this to the ovirt users maliing list, so you can get a more appropriate guidence there.
Regards, Maor
On Fri, Apr 20, 2018 at 11:06 AM, Hanna Terentieva < h.terentieva@storware.eu> wrote:
Hi Maor,
We encountered an issue with hotplugging disks when trying to attach a disk to client's envirtonment. The disk attachment request:
<disk_attachment> <bootable>false</bootable> <interface>virtio</interface> <active>true</active> <disk id="a016b350-87ef-4c3b-b150-024907fed9c0"/> </disk_attachment>
returns this error:
Error: HTTP response code is "400". HTTP response message is "Bad Request". org.ovirt.engine.sdk4.internal.services.ServiceImpl.throwErr or(ServiceImpl.java:113) org.ovirt.engine.sdk4.internal.services.ServiceImpl.checkFau lt(ServiceImpl.java:40) org.ovirt.engine.sdk4.internal.services.DiskAttachmentsServi ceImpl$AddRequestImpl.send(DiskAttachmentsServiceImpl.java:111) org.ovirt.engine.sdk4.internal.services.DiskAttachmentsServi ceImpl$AddRequestImpl.send(DiskAttachmentsServiceImpl.java:48)
oVirt version 4.2.2. The issue happened around 2018-04-17 07:57. Attaching the log. Clould you please help with the problem?
--
Pozdrawiam\Best Regards Hanna Terentieva Junior Java Developer e-mail: h.terentieva@storware.eu
*<image001.png>* <http://www.storware.eu/>
*ul. Leszno 8/44 01-192 Warszawa www.storware.eu <https://www.storware.eu/>*
*<image002.png>* <https://www.facebook.com/storware>
*<image003.png>* <https://twitter.com/storware>
*<image004.png>* <https://www.linkedin.com/company/storware>
*<image005.png>* <https://www.youtube.com/channel/UCKvLitYPyAplBctXibFWrkw>
--
Pozdrawiam\Best Regards Hanna Terentieva Junior Java Developer e-mail: h.terentieva@storware.eu
*<image001.png>* <http://www.storware.eu/>
*ul. Leszno 8/44 01-192 Warszawa www.storware.eu <https://www.storware.eu/>*
*<image002.png>* <https://www.facebook.com/storware>
*<image003.png>* <https://twitter.com/storware>
*<image004.png>* <https://www.linkedin.com/company/storware>
*<image005.png>* <https://www.youtube.com/channel/UCKvLitYPyAplBctXibFWrkw>
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users