Hello,
I am currently fighting with attaching an iso to a vm's cdrom. There are two
isos in the iso domain (A-Iso-Installer.iso and The-Iso-Installer.iso for our
purposes), I can confirm the iso domain is attached to the cluster and
everything is green. When attempting to attach the iso to the vm, I can see the
pre and post output of the "/ovirt-engine/api/vms/<uuid>/cdroms" request, it
shows the file id changing according to what the iso domain has available.
However, whenever i attempt to power on the vm, from either the api or through
the web interface, I get "Invalid ISO image path". Editing the vm through the
web interface reveals that the "Attach CD" dropdown has selected the first iso
("A-Iso-Installer.iso", and I am trying to use the second). I ran a list
against the cdrom service, found no issues with the xml that was returned. I
confirmed that listing out available isos on the iso domain results in the
expected id that I matched in the cdrom service of the vm from the api. If I ch
oose the correct iso from the gui and save, the output looks the same as the
api listing.
Before and After gist:
https://gist.github.com/robotman321/909255cbdc36fa62b730a953807f7397
The code im using to set the cdrom is the following:
https://gist.github.com/robotman321/35617c96b96b329d5d1476e015aa9898
I did note that when i would run the update api code, it does change SOMETHING
as when i go into the web interface the "Attach CD" value has gone back to the
top value in the dropdown (the wrong iso).
Has anyone seen this before, please tell me it's right in front of me, any help
is appreciated.
Thank you,
Brad
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/NBYCK56MQK4PRDCMKRROXFYMGGGO2X4L/
