On Wed, Aug 25, 2021 at 12:57 PM <csabany@freemail.hu> wrote:
Hi,
I managed a ovirt 4.4.7 for production systems. Last week i removed the Master storage domain (moved tamplates, vm-s well, unattached, etc), but i forgot to move isos. Now, when i upload a new iso to a data storage domain, the system show it, but it's unbootable: "could not read from cdrom code 0005"
This sounds like booting from an empty image. I think we have a bug when uploading from the UI "works" very quickly without uploading anything. If I remember correctly, clicking "Test connection" in the upload dialog helps to workaround this issue. You can always upload using SDK upload_disk.py example: $ cat /home/nsoffer/.config/ovirt.conf [myengine] engine_url = https://myengine.com username = admin@internal password = mypassword cafile = /home/me/certs/myengine.pem $ python3 /usr/share/doc/python3-ovirt-engine-sdk4/examples/upload_disk.py -c myengine --sd-name mystoragedomain foo.iso This way is not affected by the test connection bug and it is also faster, more powerful, and can be automated. Nir