maas 1.7.1-rc1 fails discovery
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-installer |
Fix Released
|
Medium
|
Adam Stokes |
Bug Description
Maas 1.7.1~rc1+bzr3322 on Ubuntu 14.04.1 fails the discovery process.
I have just reinstalled my maas server and configured it to my last working state. (My 3rd reinstall so I am getting proficient at it with my script.)
I PXE boot my client server. It gets an IP address, boots the kernel, loads the initrd and boots up to a login prompt. It then starts the discovery process and gives me:
Cloud-init v. 0.7.5 running 'modules:final' at Thu, 18 Dec 2014 20:19:59 +0000. Up 59.57 seconds. 2014-12-18 20:19:59,991 - util.py[WARNING]: Running ssh-authkey-
Then it just sits there and does nothing and never shows up in the Nodes list. This used to work until I upgraded from 1.7.0 to 1.7.1~rc1. I discovered this when my discovered and commissioned nodes started to fail to deploy. After backtracking all the way back to reinstalling the maas server I believe that it is a problem with 1.7.1~rc1.
Does anyone have any suggestions for a fix? Or an easy way to downgrade back to 1.7.0?
Changed in cloud-installer: | |
status: | New → Triaged |
Changed in cloud-installer: | |
status: | Fix Committed → Fix Released |
I totally reinstalled from the 14.04 iso and am running maas 1.5.4 and the discovery and commissioning works fine there.