[04:20] <mup> Bug #1750862 changed: stress-ng-cpu short runs forever on Huawei Server <MAAS:Expired> <https://launchpad.net/bugs/1750862>
[06:55] <McL0v1n> Hey hey!
[06:55] <McL0v1n> Anyone around? I've got a question.
[06:56] <McL0v1n> I'm having issues with MAAS losing IPMI capabilities. Everything will be good in the interface, but then suddenly all nodes power status switches to error and maas can't do anything. All usernames and passwords are still configured
[09:00] <mup> Bug #1766528 opened: Charm deploys fail with EOF when one Regiond daemon is missing on one MAAS node in HA MAAS <MAAS:New> <https://launchpad.net/bugs/1766528>
[09:15] <mup> Bug #1766528 changed: Charm deploys fail with EOF when one Regiond daemon is missing on one MAAS node in HA MAAS <MAAS:New> <https://launchpad.net/bugs/1766528>
[09:18] <mup> Bug #1766528 opened: Charm deploys fail with EOF when one Regiond daemon is missing on one MAAS node in HA MAAS <MAAS:New> <https://launchpad.net/bugs/1766528>
[15:04] <mup> Bug #1074317 opened: cmdline acquire and start is difficult <cli> <MAAS:Triaged> <https://launchpad.net/bugs/1074317>
[15:25] <mup> Bug #1766637 opened: UEFI-mode Bionic deployments failing <hwcert-server> <curtin:New> <MAAS:Incomplete> <https://launchpad.net/bugs/1766637>
[15:31] <mup> Bug #1766637 changed: UEFI-mode Bionic deployments failing <hwcert-server> <curtin:New> <MAAS:Incomplete> <https://launchpad.net/bugs/1766637>
[15:34] <mup> Bug #1766637 opened: UEFI-mode Bionic deployments failing <hwcert-server> <curtin:New> <MAAS:Incomplete> <https://launchpad.net/bugs/1766637>
[16:05] <McL0v1n> Good day!
[16:06] <McL0v1n> anyone around today? Still having issues with IPMI and maas
[16:19] <mup> Bug #1766651 opened: broken layout on the action dropdown for "test hardware" <MAAS:New for deadlight> <https://launchpad.net/bugs/1766651>
[16:25] <mup> Bug #1766637 changed: UEFI-mode Bionic deployments failing <hwcert-server> <curtin:Invalid> <MAAS:Invalid> <https://launchpad.net/bugs/1766637>
[16:26] <roaksoax> McL0v1n: Hi. What issues are you having ?
[16:27] <McL0v1n> SO, I had everything in maas ready to deploy. 11 nodes, 3 of which were already juju controllers
[16:27] <McL0v1n> then suddenly ipmi error on every single one
[16:27] <McL0v1n> sorry, power error
[16:27] <McL0v1n> so the status on every single one is at error
[16:27] <McL0v1n> I tried my old work around by changing the timeout in ipmi.py, but nothing yet brings it back
[16:29] <McL0v1n> roaksoax
[16:30] <McL0v1n_> Joined here, had ti leave the house
[16:34] <McL0v1n> Sorry about that
[16:41] <roaksoax> McL0v1n: so, hold on
[16:41] <roaksoax> McL0v1n: you mean you enlist/commission the machines just fine
[16:41] <roaksoax> McL0v1n: they are marked 'Ready'
[16:41] <roaksoax> McL0v1n: and after a few minutes, power is red ?
[17:15] <mimizone> Hi all. Anything that changed in the MAAS DHCP recently that would allow to set IP from different pools based on what either the relay that sent the request to MAAS or the MAC address of the server? Our IPs are segmented by rack (a few /25 per rack) and its' necessary for getting a working L3 routing in ToR switch that the right IPs are assigned by MAAS.
[17:15] <mimizone> I'd like to only use one or two MAAS region controllers for our entire setup and not have rack controllers in every racks
[17:18] <McL0v1n_> Roaksoax it wasnt after a few minutes, it was all day
[17:19] <McL0v1n_> They are all ready, and 3 are even deployed
[17:19] <McL0v1n_> Then at a certain time im sitting there configuring juju charms to prepare for a deployment and all power statuses turn error
[17:40] <mup> Bug #1766665 opened: maas-region fails with an error 500 in an attempt to delete a subnet <MAAS:Incomplete> <https://launchpad.net/bugs/1766665>
[18:06] <McL0v1n_> Roaksoax: i checked tbe logs and there isnt anything out of the ordinary
[18:13] <mup> Bug #1766671 opened: [2.4] 2018-04-24 17:49:06 maasserver.dhcp: [critical] None         (UNABLE TO OBTAIN TRACEBACK FROM EVENT) <MAAS:Triaged> <https://launchpad.net/bugs/1766671>
[18:23] <xygnal> so....we just deployed a node as a user
[18:23] <xygnal> but that node was allocated to another user
[18:24] <xygnal> this was done with non-admin keys for the 2 users
[18:24] <xygnal> is this known?
[18:43] <mup> Bug #1766680 opened: [2.4, regression] UI action confirmation messages are missing <regression> <MAAS:Triaged> <https://launchpad.net/bugs/1766680>
[18:47] <eduardo_> Hi all. If you have Debian images that are working with MAAS, send me a message. We'd like to offer $100 per working image
[18:54] <eduardo_> Same thing for Fedora, CoreOS, RancherOS
[19:08] <xygnal> disregard - mistake
[19:49] <mup> Bug #1766707 opened: [2.4, UI] Dismissing an error on the UI, will make it never appear again <MAAS:Triaged> <https://launchpad.net/bugs/1766707>
[22:52] <ltrager> eduardo_: Canonical provides paid support and may be able to assist you in deploying other operating systems
[22:52] <ltrager> eduardo_: Feel free to reach out at https://maas.io/contact-us
[23:28] <eduardo_> Thank ou ltrager but you can't buy from them even if you want to. sales is horrible so I can't even imagine support