data storage domain iso upload problem
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" thanks csabany
Hi csabany, I have tried to reproduce this by: 1. Uploading ISO to data domain, verifying that I can boot from it 2. Destroy the data domain 3. Create a new data domain, re-upload the ISO 4. Boot from the ISO The issue you have described did not reproduce. Are my steps accurate? Please provide more information - logs, what ISO do you use, how did you upload ISO to data domain, etc. Best regards, Mark
Hi Mark, This list is correct, but i have destroyed the master storage domain (i have 6-7 Sd), and after this i tried to upload ISO-s (old isos, and new isos) they were unbootable. ISO-s: Rocky8, ubuntu18, win10, debian10 etc. But i tried to use the upload_disk.py (thanksNir Soffer) and this script works fine. Best, csabany -------- Eredeti levél -------- Feladó: Mark Kemel < mkemel@redhat.com (Link -> mailto:mkemel@redhat.com) > Dátum: 2021 szeptember 5 21:40:22 Tárgy: [ovirt-users] Re: data storage domain iso upload problem Címzett: users@ovirt.org (Link -> mailto:users@ovirt.org) Hi csabany, I have tried to reproduce this by: 1. Uploading ISO to data domain, verifying that I can boot from it 2. Destroy the data domain 3. Create a new data domain, re-upload the ISO 4. Boot from the ISO The issue you have described did not reproduce. Are my steps accurate? Please provide more information - logs, what ISO do you use, how did you upload ISO to data domain, etc. Best regards, Mark _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/SQKNPNJ7T6VIT5...
On Mon, Sep 6, 2021 at 11:03 AM Nyika Csaba <csabany@freemail.hu> wrote:
Hi Mark,
This list is correct, but i have destroyed the master storage domain (i have 6-7 Sd), and after this i tried to upload ISO-s (old isos, and new isos) they were unbootable. ISO-s: Rocky8, ubuntu18, win10, debian10 etc.
But i tried to use the upload_disk.py (thanksNir Soffer) and this script works fine.
We already have bug for this issue, this is not related to the "Test connection" bug: https://bugzilla.redhat.com/1977276 This should be fixed soon upstream, but I'm not sure when the fix will be released. Nir
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
On Sun, Sep 5, 2021 at 11:27 PM Nir Soffer <nsoffer@redhat.com> wrote:
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.
Reproduced locally, upload fails in engine, but the UI does not show the failure, and an empty disk is left. Nyika, see the attached screenshot. Is this what you get?
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
Hi, Thanks for advice. I saw the picture and yes, this what i got. I tried the "Test connection" button, and that was OK, but the uploaded iso didn't work, BUT the "upload_disk.py" scipt works fine! Thank You! csabany -------- Eredeti levél -------- Feladó: Nir Soffer < nsoffer@redhat.com (Link -> mailto:nsoffer@redhat.com) > Dátum: 2021 szeptember 5 23:20:19 Tárgy: Re: [ovirt-users] data storage domain iso upload problem Címzett: Nyika Csaba < csabany@freemail.hu (Link -> mailto:csabany@freemail.hu) > On Sun, Sep 5, 2021 at 11:27 PM Nir Soffer <nsoffer@redhat.com> wrote:
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.
Reproduced locally, upload fails in engine, but the UI does not show the failure, and an empty disk is left. Nyika, see the attached screenshot. Is this what you get?
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
participants (4)
-
csabany＠freemail.hu -
Mark Kemel -
Nir Soffer -
Nyika Csaba