Actions
Bug #25987
closedAPIv4 | Creating VM results in creation of stateless desktop
Description
I've been grinding my teeth with this one. I've created a new oVirt Compute Resource and selected to use v4 API (experimental)... I know, it's experimental...
However, looking at oVirt it seems the VM is created as stateless desktop, which, as far as I can tell from reading up and testing this out, results in the VM's hard drive being reset to day 0. However, in the beginning there was no OS, meaning everything starts to fail and I had to redeploy my windows. Luckily I noticed this and could revert the setting; still, it shouldn't create a stateless anything as a default, IMO? Or am I missing the bigger picture here?
Updated by Tomer Brisker almost 6 years ago
- Related to Bug #24808: Updating Host cause the parameters Stateless,Start in Pause Mode and Delete Protection be checked. added
Updated by Shira Maximov almost 6 years ago
- Is duplicate of Bug #24808: Updating Host cause the parameters Stateless,Start in Pause Mode and Delete Protection be checked. added
Updated by Shira Maximov almost 6 years ago
- Status changed from New to Duplicate
Updated by Shira Maximov almost 6 years ago
- Related to deleted (Bug #24808: Updating Host cause the parameters Stateless,Start in Pause Mode and Delete Protection be checked.)
Actions