Thanks all! I’ve solved the issue, problem was in network configuration and incorrect api url in rack-controllers config,
Andrey Bashlakov [email protected]<mailto:[email protected]> 26 янв. 2018 г., в 1:56, Dmitrii Shcherbakov <[email protected]<mailto:[email protected]>> написал(а): Hi Andrei, You could also build a temporary image with a backdoor (the doc below is not yet published at docs.ubuntu.com<http://docs.ubuntu.com/>): https://github.com/CanonicalLtd/maas-docs/blob/master/en/troubleshoot-faq.md#backdoor-image-login https://github.com/CanonicalLtd/maas-docs/issues/612 (original doc request) I had to do this a few times when debugging very early-stage issues and there is nothing more to it than unpacking the original image, adding a hashed password entry to /etc/shadow and repacking it back (to a squashfs). The reason for re-packing is that cloud images are left untouched by MAAS - it doesn't unpack them prior to sending to a node and they receive metadata from MAAS over a network. So if MAAS cannot be successfully queried for metadata from an ephemeral system but the image itself gets there this is a reliable way to hack your credentials in. If you go with that approach make sure to restore the original image after you get rid of the original problem. Best Regards, Dmitrii Shcherbakov Field Software Engineer IRC (freenode): Dmitrii-Sh On Thu, Jan 25, 2018 at 12:59 PM, Andres Rodriguez <[email protected]<mailto:[email protected]>> wrote: 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]<mailto:[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<http://www.vk.com/> -- Maas-devel mailing list [email protected]<mailto:[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]<mailto:[email protected]> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/maas-devel
-- Maas-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/maas-devel
