Hello I'm using Foreman 1.13 and oVirt 4.0.4 and I have an oVirt template with 2 disks, both with data, from which I want to spin-up new VMs via Foreman.
If I create the VM from Foreman everything is correct, the 2 disks are the ones set in the oVirt template. But if I try from hammer CLI like this: $ hammer host create --hostgroup-id=13 --compute-resource="My oVirt Resource" --provision-method="image" --image="MyImage" --name="test-01" --compute-attributes="start=1" --operatingsystem-id=2 Then, the new VM has only the "base" disk. And if I try like this $ hammer host create --hostgroup-id=13 --compute-resource="My oVirt Resource" --provision-method="image" --image="MyImage" --name="test-01" --compute-attributes="start=1" --operatingsystem-id=2 --volume="size_gb=8,storage_domain=ba2bd397-9222-424d-aecc-eb652c0169d9,bootable=true" --volume="size_gb=25,storage_domain=ba2bd397-9222-424d-aecc-eb652c0169d9,bootable=false" Then 2 disks are created and attached but the second one (the 25GB disk) is a brand new disk and not a copy of the disk attached to the original template. Is this an Hammer bug? Has anyone got this working? Thanks in advance -- Davide -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
