Hi Andrei, If the enlistment script fails, it will automatically create a user/password that should be displayed to you in the console.
That said, you don't necessarily need access to the enlistment to determine what the issue may be. I suggest you look in /var/log/maas/rsyslog/ where you should be able to find the logs of the enlistment machine, which should show you what may be going wrong. I suspect this is due to it not being able to install packages. Hope this helps. On Wed, Jan 24, 2018 at 6:48 PM, Bashlakov Andrei <[email protected]> wrote: > Hi all! > > I have a troubles with deploying MaaS rack-controller in network, that has > strict access restrictions and non-trivial DNS configuration. At this > moment all machines that boot via PXE from dedicated rack-controller > stopped at login prompt at enlisting stage. There is no logs on region > controller nor errors on machines screens nor any information about this > machines in MaaS interface. I've dumped machines traffic and investigate it > for any errors like problems in connection establishment, but all > connections seems to be fine. Machines successfully get boot images from > rack-controller and enlisting script from region-controller. Is there any > possibility to login to machines at this state and get any logs from them? > Or maybe there is other way to debug this problem? > > Well be glad for any advice. > > Best regards, > Andrey Bashlakov > R&D Engineer > www.vk.com > -- > Maas-devel mailing list > [email protected] > Modify settings or unsubscribe at: https://lists.ubuntu.com/ > mailman/listinfo/maas-devel > -- Andres Rodriguez Engineering Manager, MAAS Canonical USA, Inc.
-- Maas-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/maas-devel
