I’m learning more and more about Foreman every day and really excited to use it!
We are running Foreman 16 on CentOS 7.
When creating a new VM I notice that some of the “hw” is not created as requested on the Foreman form - RAM usually works fine but the CPU/Core count is wrong, the disk is created as Thick although i checked Thin, can’t create an additional disk and some of the vm options are wrong.
Am I missing something? should I “fix” this by making a provisioning template that will confirm my hw needs?
Should I Use the provisioning template to fix this? any ideas what the issue is? @tbrisker - I see that you make a change on the screen shot? Its not showing on the actual message but I got a notification that you edited it…
I guess this might be a bug because you are cloning the host from a vmware template. What Foreman does under the hood is cloning the template vm and then customizing the hardware. I think, making the disk thin provisioned either does not work at all or it’s not implemented correctly. Your provisioning template has nothing to do with this process, it’s Foreman (or the library we use to connect with vmware api).
I’d suggest opening an issue in our issue tracker (projects.theforeman.org) and say, that when you clone a VM on VMWare, it doesn’t customize all the fields.