maas 1.7.1-rc1 fails discovery

Bug #1404014 reported by Daniel Bidwell
8
This bug affects 1 person
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-fingerprints () failed ec2: ec2: ####...#### ec2: -----BEGIN SSH HOST KEY FINGERPRINTS----- ec2: -----END SSH HOST KEY FINGERPRINTS----- ec2: ####...#### Cloud-init v. 0.7.5 finished at Thu, 18 Dec 2014 20:20:00 +0000. Datasource DataSourceNone. Up 59.70 seconds 2014-12-18 20:20:00,017 - cc_final_message.py[WARNING]: Used fallback datasource

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?

Tags: 1.7.1 maas
Revision history for this message
Daniel Bidwell (bidwell) wrote :

I totally reinstalled from the 14.04 iso and am running maas 1.5.4 and the discovery and commissioning works fine there.

Revision history for this message
Adam Stokes (adam-stokes) wrote :

Did it work with 1.7.0 release as well? This could be a bug in MAAS specifically from 1.7.0 to 1.7.1

Changed in cloud-installer:
importance: Undecided → Medium
assignee: nobody → Adam Stokes (adam-stokes)
milestone: none → v0.22
Changed in cloud-installer:
status: New → Triaged
Revision history for this message
Daniel Bidwell (bidwell) wrote :

I think that it worked correctly in 1.7.0, but getting back to 1.7.0 looked like more work than it was worth.

Revision history for this message
Adam Stokes (adam-stokes) wrote :

Thanks, I'll do some runs with 1.7.1 and see if I can reproduce

Revision history for this message
Adam Stokes (adam-stokes) wrote :

Daniel, do you mind trying the packages in our experimental ppa? I've tested this on maas 1.7.0, 1.7.1-rc1-rc4 and haven't run into those particular issues.

Thanks!

Changed in cloud-installer:
status: Triaged → In Progress
Revision history for this message
Daniel Bidwell (bidwell) wrote : Re: [Bug 1404014] Re: maas 1.7.1-rc1 fails discovery

OK, I reinstalled the maas machine from 14.04.1 and use maas 1.7.1~rc4
+bzr3340-0ubuntu1~trusty1 and the problem went away. My machines now
install to the disk again. Thanks. It works again.

On Fri, 2015-01-23 at 22:39 +0000, Adam Stokes wrote:
> Daniel, do you mind trying the packages in our experimental ppa? I've
> tested this on maas 1.7.0, 1.7.1-rc1-rc4 and haven't run into those
> particular issues.
>
> Thanks!
>
> ** Changed in: cloud-installer
> Status: Triaged => In Progress
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1404014
>
> Title:
> maas 1.7.1-rc1 fails discovery
>
> Status in Ubuntu Openstack installer:
> In Progress
>
> 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-fingerprints () failed ec2: ec2:
> ####...#### ec2: -----BEGIN SSH HOST KEY FINGERPRINTS----- ec2:
> -----END SSH HOST KEY FINGERPRINTS----- ec2: ####...#### Cloud-init v.
> 0.7.5 finished at Thu, 18 Dec 2014 20:20:00 +0000. Datasource
> DataSourceNone. Up 59.70 seconds 2014-12-18 20:20:00,017 -
> cc_final_message.py[WARNING]: Used fallback datasource
>
> 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?
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cloud-installer/+bug/1404014/+subscriptions
>
>

--
Daniel R. Bidwell | <email address hidden>
Andrews University | Information Technology Services
If two always agree, one of them is unnecessary
Karma is getting what you deserve, mercy is not getting what you
deserve,
grace is getting what you do not deserve.
"In theory, theory and practice are the same.
In practice, however, they are not."

Revision history for this message
Adam Stokes (adam-stokes) wrote :

Thanks Daniel, glad to here it!

Changed in cloud-installer:
status: In Progress → Fix Committed
Changed in cloud-installer:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.