unable to locate and access the MAAS controller during maas-test run
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
maas-test |
Triaged
|
Medium
|
Unassigned |
Bug Description
during maas-test run, a VM is created and configured via cloud-init. That VM then has MAAS installed on it for the testing.
Problems:
1: The MAAS VM has an unpredictable randomly assigned DHCP address. This makes it difficult to find. I had to resort to 'arp -an' to find an active IP address on what I think was the VM network.
2: Once I have this IP address, I can access the MAAS dashboard, but am unable to login because while the User name is always admin, the password is randomly generated and I have no idea until AFTER the run is complete what that password is.
3: The maas-test script DOES tell me the URL, ssh info, login name and randomly generated password, BUT it doesn't tell me this info until AFTER testing is complete and the VM is destroyed. This is the LAST bit of output I get before maas-test exits.
To fix 1: the MAAS Node should get a predictable IP address, not a randomly assigned one.
To fix 2: the username and password should be stable and known. It's a test tool, so a randomly generated password is unnecessary. Stick with something easy to remember like admin/insecure
To fix 3: the login data should appear BEFORE testing begins, e.g. between the step where MAAS is installed on the VM and where test_power_up_node begins.
Changed in maas-test: | |
status: | New → Triaged |
importance: | Undecided → Medium |
> To fix 1: the MAAS Node should get a predictable IP address, not a randomly assigned one.
The IP address is assigned by uvtool (which, in turn, uses kvm)… not sure it's possible to get the same IP address every time, but I'll see if it's doable.
> To fix 2: the username and password should be stable and known. It's a test tool, so a randomly generated password is unnecessary. Stick with something easy to remember like admin/insecure
You're right, I'll change that.
> To fix 3: the login data should appear BEFORE testing begins, e.g. between the step where MAAS is installed on the VM and where test_power_up_node begins.
This is already the case, see http:// bazaar. launchpad. net/~maas- maintainers/ maas-test/ trunk/view/ head:/maastest/ cases.py# L158