Maybe I'm using am incompatible base OS. What are others testing MAAS with? sent from my android phone <div class="gmail_quote">On Apr 18, 2012 12:29 PM, "Michael Hughes" <<a href="mailto:itismike@gmail.com">itismike@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> I restarted the nodes and the MAAS servers but still do not see completion. Perhaps I should have mentioned this earlier, but when I examine the nodes they have successfully booted via PXE and display their network settings, then they drop to a initramfs shell after exhibiting these errors: - iscsistart: cannot make connection to 10.x.x.x:3260 (-1,101) - Gave up waiting for root device The 10.x.x.x IP address is the External NIC on my MAAS server. MAAS DHCP is giving out IPs in the 172 range. I don't know much about iSCSI, but shouldn't the connections go back to the card on my Internal network (172.x.x.x)? During installation, the auto-discovery of the MAAS DHCP installation step defaulted to the 10.x.x.x address. At the time I figured that is the 'gateway' for the nodes to reach the Internet so I accepted it. However I've since run 'dpkg-reconfigure maas-dhcp' and manually changed my gateway to the 172 address, yet when the nodes reboot and report their network settings they're still listing 10 as their gateway. On Tue, Apr 17, 2012 at 6:00 PM, Francis J. Lacoste <<a href="mailto:francis.lacoste@canonical.com">francis.lacoste@canonical.com</a>> wrote: > Hi Michael, > > If you updated the ephemeral image, you should simply need to > power-cycle the machines in 'Commissioning' state and the process should > now complete successfully. The nodes should appear as 'Ready' afterwards. > > Cheers > > On 12-04-17 01:58 PM, Michael Hughes wrote: >> Thanks for the pointer Francis. I tried that solution yesterday per >> Robbie Williamson's suggestion (hi Robbie!) but the directory >> structure was not valid (i.e.: somewhere around 'ephemeral/' the >> folders in the solution didn't match those on my system. For the >> record, I was using yesterday's daily build of 12.04 with both the >> Stable and Testing PPAs of MAAS installed.) >> >> The folder structure explained in the linked bug exists in my current >> build (using this morning's 12.04 daily build of Server and no >> additional PPAs,) but after throwing some perl locale warnings it >> completes with: >> "Leaving 'diversion of /etc/init/ureadahead.conf to >> /etc/init/ureadahead.conf.disabled by cloud-init' >> and I notice nothing new in my web interface. Do I need to >> reinstall/reconfigure MAAS at this point, and if so how? >> >> Thanks! >> -Mike >> >> On Tue, Apr 17, 2012 at 1:22 PM, Francis J. Lacoste >> <<a href="mailto:francis.lacoste@canonical.com">francis.lacoste@canonical.com</a>> wrote: >>> On 12-04-17 10:00 AM, Michael Hughes wrote: >>>> Hi Devels. I'm trying to follow along with the MAAS wiki: >>>> <a href="https://wiki.ubuntu.com/ServerTeam/MAAS" target="_blank">https://wiki.ubuntu.com/ServerTeam/MAAS</a> but I must be missing >>>> something because I never get the opportunity to Accept & Commission >>>> the nodes. It just says 'Commissioning' without progressing. >>>> >>>> My attempts consisted of: >>>> - Download and install the latest daily build of Precise 64-bit >>>> choosing "Ubuntu MAAS Installation" from the install menu >>>> - apt-get update; apt-get upgrade >>>> - Follow the steps on the above wiki to build and activate the MAAS server >>>> >>>> I also tried adding the Stable, Testing, and Dailybuild MAAS PPAs >>>> prior to upgrading. Stable and Testing compiled fine: my three nodes >>>> were able to be added via MAC address and booted to PXE, but the web >>>> management page never showed the Accept & Commission button for my >>>> nodes. Dailybuilds failed to install citing authentication errors. >>>> Reading the archives I see Testing isn't appropriate, and I didn't >>>> expect Dailybuild to work without glitches, but thought Stable would >>>> be a close match to the wiki. If not, where are the screenshots on the >>>> wiki coming from? >>>> >>> >>> That's because the ephemeral image uses the latest released version >>> which is beta2. Unfortunately, the version of cloud-init in beta2 >>> doesn't know about MAAS yet. >>> >>> <a href="https://bugs.launchpad.net/ubuntu/+source/maas/+bug/981845" target="_blank">https://bugs.launchpad.net/ubuntu/+source/maas/+bug/981845</a> >>> >>> Comment #2 there has the work-around. You basically need to upgrade >>> cloud-init in the ephemeral images used for commissioning. >>> >>> Let me know if you need more help. >>> >>> Cheers >>> >>> -- >>> Francis J. Lacoste >>> <a href="mailto:francis.lacoste@canonical.com">francis.lacoste@canonical.com</a> >>> >>> >>> -- >>> Mailing list: <a href="https://launchpad.net/~maas-devel" target="_blank">https://launchpad.net/~maas-devel</a> >>> Post to : <a href="mailto:maas-devel@lists.launchpad.net">maas-devel@lists.launchpad.net</a> >>> Unsubscribe : <a href="https://launchpad.net/~maas-devel" target="_blank">https://launchpad.net/~maas-devel</a> >>> More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a> >>> > > -- > Francis J. Lacoste > <a href="mailto:francis.lacoste@canonical.com">francis.lacoste@canonical.com</a> > </blockquote></div>