setup_vm - trouble running all local servers simultaneously
Bug #1170767 reported by
Julien Funk
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
u1-test-utils |
Incomplete
|
High
|
Vincent Ladeuil |
Bug Description
After isntalling setup_vm and running the following steps:
./bin/setup_vm.py --install sso
./bin/setup_vm.py --install pay
./bin/setup_vm.py --install u1
virsh start sso
ssh <email address hidden> // WORKS
- in the sso local machine, in ~/bin run: run-for-u1
- on the host machine: virsh start pay
ssh <email address hidden> // DOES NOT CONNECT
After the above steps I am unable to log into the sso instance either which was working previously. Leo has mentioned he sees the exact same problem on his machine and was necessary to workaround.
Attached is the .console log from ~/images as well as my vms.conf file.
Changed in u1-test-utils: | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → Vincent Ladeuil (vila) |
To post a comment you must log in.
vms.conf removed, it contained a ppa password that shouldn't appear there, better edit it next time before uploading ;)
Nothing wrong there anyway, there was a 'sk_size=16G' instead of 'disk_size=16G' but that was probably a copy/paste error (boudle-check your local copy just in case).
As for the precise- server- pristine. console file, this one seems fine but pay.console may be more appropriate.
Just a note that may not be obvious for newcomers: as soon as you use a disk image as a backing for another vm, you should not use the the original image or weird things can happen (this may deserve its own bug if people run into this issue too often though).
The 'backing' paradigm requires to re-install any backed on vm as soon as the pristine vm is used (for tests or checking).