Hammer CLI, oVirt and templates

Support
1

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
2

Solved. I have to specify in the Instance Type the 2-disks template,
specifying only the image wasn't enough. I guess the confusion (at least
for me) comes from the fact that oVirt UI has no clear distinction between
"image" and "template", where Foreman clearly has.

··· On Tuesday, October 18, 2016 at 3:35:19 PM UTC+2, dav...@billymob.com wrote: > > > Is this an Hammer bug? Has anyone got this working? > >