VMs not reflected in virt-manager
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo-quickstart |
Expired
|
Undecided
|
Unassigned |
Bug Description
When running the quickstart.sh on my local (centos7) box, the resulting VMs are not reflected in virt-manager, which is confusing if you're coming from instack-virt-setup (where they are).
It's even more confusing if you misread the README and accidentally do this:
sudo ./quickstart.sh localhost
What happens is the VMs *are* visible in virt-manager, only it fails to boot the undercloud due to permissions caused by putting the undercloud image in /root due to the sudo.
When you then re-run without the sudo, the VMs remain in virt-manager, but never boot, which from a new-user perspective is going to be a source of confusion I think.
At the least I think we need an addition to the "Virtual environment setup complete" notes output when the VMs have been launched, because if I've say run the quickstart.sh as "shardy" they are completely invisible which is magical and confusing until you understand what's going on.
So, to clarify here's what I did:
Cloned tripleo-quickstart
cd tripleo-quickstart
sudo ./quickstart.sh --install-deps
sudo ./quickstart.sh localhost
Note I forgot to remove the "sudo" in the second call (this is correct in the README but could probably use emphasis as I'm assuming others may make a similar error).
What then happens is it dowloads and caches the images in /root/oooq_cache, adds the VMs (which are visible in virt-manager) then fails with a permissions error trying to boot the VM from the image in /root
Re-running without sudo works fine, but it's then non-obvious (for an ex instack-virt-setup user) where the VMs are.
Note all steps were performed via my user "shardy" account, which is setup to allow sudo access.