BOunce your nodes. I was stuck on this for almost a week. Your servers aren't responding to the "Wake On LAN" or whatever "remote"method you are trying to use to wake up the servers.
After you setup your MAAS controller, you "power-on" your servers. If DHCP/DNS is setup right, they PXE boot and load a version of the OS that is used for "Declaring" the server to the MAAS controller. At that point they show up in your "Nodes" list as declared. You select the server and click on "Accept and Commission"...then they stay there, never changing. For me, this meant that the PXE command to boot to the new "commissioning" OS was IGNORED by my servers. I simply turned them on and voila....about 10 minutes later, they are completely configured and "Ready". Hope that helps you folks out there and you have hair left....I pulled all mine out before I figured out what I need to do....hmmmm.....maybe the hair was holding me up! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/992075 Title: Commissioning status persists with cloud-init 0.6.3-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/992075/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
