=== axw_ is now known as axw
[04:43] <sentinel_> anyone here willing to help a newbie
[05:08] <sentinel_> ....
[05:51] <sentinel_> hi catbus
[05:53] <catbus> sentinel_: hi
[05:57] <sentinel_> hey catbus how well do you know maas
=== frankban|afk is now known as frankban
=== frankban is now known as frankban|afk
=== frankban|afk is now known as frankban
[17:21] <bdx> https://bugs.launchpad.net/juju/+bug/1736022
[17:21] <bdx> ^^^^^
=== frankban is now known as frankban|afk
[18:19] <trdillon1> Hello. I can't commission some HPE BL460c G9s
[18:19] <trdillon1> They all fail the lshw script with a segfault
[18:19] <trdillon1> MAAS 2.2
[18:29] <jgerardopine> Hi everybody, I have a question. When running maas <user> rack-controllers read there is a value for the following element: current_commissioning_result_id
[18:30] <jgerardopine> I 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 ready
[18:31] <jgerardopine> and what would be the result id?
[18:31] <jgerardopine> the 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 ready
[18:41] <trdillon1> Why would lshw segfault on a commission?
[19:20] <trdillon1> lshw works fine when i keep the machine up and ssh into it
[22:53] <trdillon1> My 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] <sathackr> can 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] <sathackr> and if there is a way to change it?
[22:54] <sathackr> s/commissioning/deployment