/srv/irclogs.ubuntu.com/2017/12/04/#maas.txt

=== axw_ is now known as axw
sentinel_anyone here willing to help a newbie04:43
sentinel_....05:08
sentinel_hi catbus05:51
catbussentinel_: hi05:53
sentinel_hey catbus how well do you know maas05:57
=== frankban|afk is now known as frankban
=== frankban is now known as frankban|afk
=== frankban|afk is now known as frankban
bdxhttps://bugs.launchpad.net/juju/+bug/173602217:21
bdx^^^^^17:21
=== frankban is now known as frankban|afk
trdillon1Hello. I can't commission some HPE BL460c G9s18:19
trdillon1They all fail the lshw script with a segfault18:19
trdillon1MAAS 2.218:19
jgerardopineHi everybody, I have a question. When running maas <user> rack-controllers read there is a value for the following element: current_commissioning_result_id18:29
jgerardopineI am trying to evaluate when the rack controlelr is ready (green arrow in status of the MAAS GUI rack-controllers tab) But there is no STATUS on the JSON output of the above command. I was wondering if current_commissioning_result_id tells you ehn when the rack controller is ready18:30
jgerardopineand what would be the result id?18:31
jgerardopinethe reason I am asking is that I don't want to parse each service in the output to telll when my maas rack controller is ready18:31
trdillon1Why would lshw segfault on a commission?18:41
trdillon1lshw works fine when i keep the machine up and ssh into it19:20
trdillon1My issue with lshw was related to the hard drive partitioning. I booted into rescure and wiped it out. Now the blades are commissioning fine.22:53
sathackrcan anyone help me understand how maas picks which drive to boot from PXE after commissioning? I have an environment where the drive MAAS is instructing the server to boot from is not the drive that the deployment process installed grub to.22:53
sathackrand if there is a way to change it?22:53
sathackrs/commissioning/deployment22:54

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!