[00:42] <haasn> fritchie: with any luck, the “full event log” might have something relevant. Otherwise, try “keep on & start ssh” and ssh in to see if something's up
[00:42] <haasn> (I think there are log files somewhere)
[00:48] <mup> Bug #1547732 opened: [2.0] Cannot connect to UI if rack controller cannot be contacted <MAAS:Triaged> <https://launchpad.net/bugs/1547732>
[00:51] <mup> Bug #1547732 changed: [2.0] Cannot connect to UI if rack controller cannot be contacted <MAAS:Triaged> <https://launchpad.net/bugs/1547732>
[00:54] <mup> Bug #1547732 opened: [2.0] Cannot connect to UI if rack controller cannot be contacted <MAAS:Triaged> <https://launchpad.net/bugs/1547732>
[00:55] <fritchie> is there a way to force a node to ready status?
[00:57] <mup> Bug #1547732 changed: [2.0] Cannot connect to UI if rack controller cannot be contacted <MAAS:Triaged> <https://launchpad.net/bugs/1547732>
[01:00] <mup> Bug #1547732 opened: [2.0] Cannot connect to UI if rack controller cannot be contacted <MAAS:Triaged> <https://launchpad.net/bugs/1547732>
[05:41] <durschatz> I'm commissioning 5xBM (SuperMicro) + 1xKVM nodes that all suddenly 'Failed Commissioning' immediately after each PXE boots OK with Cores,RAM,Disks,Storage data is freshly populated in MAAS.  Started happening today with weeks of no issues.  Anyone have clues?
[11:07] <saket_> hi
[11:07] <saket_> anyone depolyed autopilot maas
[11:12] <saket_> hi
[11:12] <saket_> dweaver
[11:12] <saket_> do you have experiene on MAAS deployment
[11:55] <mup> Bug #1547732 changed: [2.0] Cannot connect to UI if rack controller cannot be contacted <MAAS:Fix Committed by blake-rouse> <https://launchpad.net/bugs/1547732>
[13:40] <mup> Bug #1547853 opened: commission fails after swapping HDD <maas (Ubuntu):New> <https://launchpad.net/bugs/1547853>
[14:17] <mup> Bug #1547874 opened: Region still depends on piston instead of piston3 <tech-debt> <MAAS:Triaged> <MAAS trunk:Triaged> <https://launchpad.net/bugs/1547874>
[14:20] <mup> Bug #1547874 changed: Region still depends on piston instead of piston3 <tech-debt> <MAAS:Triaged> <MAAS trunk:Triaged> <https://launchpad.net/bugs/1547874>
[14:23] <mup> Bug #1547874 opened: Region still depends on piston instead of piston3 <tech-debt> <MAAS:Triaged> <MAAS trunk:Triaged> <https://launchpad.net/bugs/1547874>
[14:47] <mup> Bug #1547877 opened: Region uses python3-requests without declaring dependency <tech-debt> <MAAS:Triaged> <MAAS trunk:Triaged> <https://launchpad.net/bugs/1547877>