@sebastian-roth Looks like the mystery continues… Below are results!
Creating the master image on a physical machine allows me to sent to any other physical machine, doesn’t need to be like models. Sending the master image built on the physical machine to a HyperV VM causes the same issue as from a HyperV master image to a physical machine. The message is below, warning that the UUID doesn’t exist and cannot boot.
When running debug deploy tasks, below are the results for the physical machine and virtual machine UUID’s respectively. They look identical… This makes me wonder why CentOS doesnt think the disk UUID exists…
The physical machine boots fine, virtual machine tries to boot and then goes to emergency mode.
From what I can tell, FOG is handling the UUID’s correctly…