[01:27] I'm looking at the backup recommendations for maas, and it says to stop postgresql, maas-{dhcp,regiond,rackd} during the backups, is that just to make sure nobody is making changes to it while you back up? seems tricky to backup the db with it down, too :) [05:52] Hi all, while deploying maas node, it got failed, how to investigate and troubleshoot, i read in maas documents asked to get into rescue mode ? [07:23] maestropandy commision goes right? [07:27] jose-phillips: commision goes well [07:28] your server have some special configuration [07:28] ? [07:28] or just a normal server with hard drive [07:28] in deployment its machine is restarting multiple times which i can able to see in console [07:28] its normal boot from pxe thats no special [07:29] on the logs [07:29] inside maas you dont have any message? [07:29] i have checked there, no error logs [07:30] but node is restarting multiple times [07:31] ok try selection the server [07:31] on actions [07:31] select rescue mode [07:32] turn on the machine and try to access in ssh [07:33] now node got failed deployment, shall i do rescue mode now ? [07:33] yep [07:33] failed deployment now allowing to rescue mode [07:34] i think cant take rescue action on failed deployment node [07:34] at least on maas 2.3 yes [07:34] i already tried [07:35] have u tried with failed deployment node or while deploying, please confirm [07:35] when the machine flag deployment failed [07:35] i set on rescue mode [07:35] and is booting up on rescue mode [07:35] mine is 2.2.2 version [07:36] shall i reset node via console and do ? [07:36] but your node is on "failed deployment" [07:36] or in "deployment" [07:37] now my node is one failed deployment [07:37] and if you select rescue mode what happend? [07:37] the selected node cannot be resuce mode, please update your selection [07:38] mhmm i already tried on 2.3 and works [07:40] any other option [07:41] ?? [07:41] flag broken node [07:41] and try to rescue mode [07:41] okay [07:41] acording the documentation im right [07:42] 2.2 can just do on deployed or broken node [07:42] now its working [07:42] took rescue mode [07:42] in 2.3 [07:42] apply for failed node [07:42] after entering rescue mode next what to do ? [07:43] idk if your hard drive will be mounted or not [07:43] i recommend you see if you have something on /var/log/syslog on your hard drive [07:43] to see if something is failing there [07:43] wbat version of os are you trying to install [07:44] no what am asking is now status in "entering rescue mode" on MAAS UI, shall i go to MAAS server and see that system logs / [07:44] no i mean on the server that is failing [07:45] mean see via console ? we have rsyslog configured with MAAS, so from maas server, i can see syslog of that server [07:45] how long status will be in resuce mode, still MAAS UI showing, "entering rescue mode" [07:46] i don't think so you are running on emphemeral disk [07:46] u mean ubutu right [07:46] yep [07:46] is ubuntu right? [07:46] i recommend you check the servers log in console via ssh [07:46] at least is what i try to do [07:47] yes i am seeing the same through rsyslog collected on MAAS server [07:48] also for another node i found "IPMI reachalbity issue " for that whether firmware upgrade will do needful how to resolve in that case [07:49] jose-phillips: in rescue mode logs, i can see "timed out waiting for reply fom ntp.ubuntu.com [07:56] jose-phillips: found, "hardware error" with CPU [07:58] thats sound more reasonable [07:59] is all that you have [07:59] is not more detailed? [08:00] another question when the node is "deploying" after restart just stuck on grub? === frankban|afk is now known as frankban [11:53] Bug #1739761 opened: Unable to deploy Precise on MaaS 2.3.0 (6434) [12:56] Bug #1739761 changed: Unable to deploy Precise on MaaS 2.3.0 (6434) === frankban is now known as frankban|afk [17:39] hi [17:39] guys [17:39] question [17:39] is posible modify a tag? [17:39] i creat a tag for kernel options per node [17:39] but i need change the kernel_opts arguments on the tag this is posible?