[00:58] <mup> Bug #1759944 changed: [2.4, UI] Changing the subnet's fabric/vlan over the UI has no effect <MAAS:Triaged by mpontillo> <MAAS 2.3:New> <https://launchpad.net/bugs/1759944>
[06:36] <mup> Bug #1759086 changed: [2.4, websockets] Only send node storage information when needed <performance> <MAAS:Won't Fix> <https://launchpad.net/bugs/1759086>
[06:54] <mup> Bug #1759085 changed: [2.4, websockets] Only send node interface data on websocket when needed <performance> <MAAS:Won't Fix> <https://launchpad.net/bugs/1759085>
[07:21] <mup> Bug #1760037 opened: [2.4, websockets] GeneralManager is caching all data on load <performance> <MAAS:Triaged> <https://launchpad.net/bugs/1760037>
[12:13] <mup> Bug #1759085 opened: [2.4, websockets] Only send node interface data on websocket when needed <performance> <MAAS:Triaged> <https://launchpad.net/bugs/1759085>
[12:13] <mup> Bug #1759086 opened: [2.4, websockets] Only send node storage information when needed <performance> <MAAS:Triaged> <https://launchpad.net/bugs/1759086>
[12:19] <mup> Bug #1759085 changed: [2.4, websockets] Only send node interface data on websocket when needed <performance> <MAAS:Triaged> <https://launchpad.net/bugs/1759085>
[12:19] <mup> Bug #1759086 changed: [2.4, websockets] Only send node storage information when needed <performance> <MAAS:Triaged> <https://launchpad.net/bugs/1759086>
[12:25] <mup> Bug #1759085 opened: [2.4, websockets] Only send node interface data on websocket when needed <performance> <MAAS:Triaged> <https://launchpad.net/bugs/1759085>
[12:25] <mup> Bug #1759086 opened: [2.4, websockets] Only send node storage information when needed <performance> <MAAS:Triaged> <https://launchpad.net/bugs/1759086>
[15:52] <karunamon> Heya folks; need to check my understanding on something. Is the "Cisco UCS Manager" power type completely equivalent to the "UCS Chassis Manager" chassis type?
[15:54] <karunamon> I can control individual UCS blades perfectly, but I'm getting "Failed to probe and enlist UCS nodes: Admin implicit props cannot be modified, class=lsbootVirtualMedia, prop=propAcl" in my region log
[15:54] <karunamon> when trying to add the entire chassis
[16:33] <roaksoax> karunamon: yes, it is the same thing, the problem may be that the API changing since first enabled and maas cannot discover all available machines
[18:39] <jac_cplane> looking for parted, fdisk in maas-enlist  when enlisting a node drops into initramfs  - any help on how I can repartion the disk when this happens
[18:39] <jac_cplane> in busybox
[18:39] <bladernr> roaksoax, blake_r how exactly does MAAS determine whether we're booted in legacy or EFI mode during commissioning?
[18:40] <bladernr> does it look for EFIVARs or is it some other method?
[18:42] <roaksoax> bladernr: in <2.3 we look at how the machine is booting *e.g. if it pxe boots and requests efi stuff
[18:42] <roaksoax> bladernr: in 2.4+ we look at /sys/firmware/efi
[18:42] <roaksoax> in thepehemral environment
[18:42] <roaksoax> + what it boots
[18:43] <bladernr> hrmmm... so does that mean it checks that every time the node boots? or still only at commissioning time?
[18:43] <roaksoax> bladernr: every time, but with newer firmware they have broken stuff
[18:43] <roaksoax> bladernr: making it non-backwards compat
[18:43] <roaksoax> which the system can be EFI but it can boot on legacy
[18:43] <roaksoax> but still require efi
[18:43] <roaksoax> so we added an ptpion to force the boot method in 2.4
[18:44] <bladernr> yeah, that seems to be the case here, trying to determine if they broke something in firmware (which is likely).
[18:45] <bladernr> is it possible to try 2.4?
[18:46] <bladernr> maas/next is showing me the same 2.3 that is in xenial-updates
[18:47] <roaksoax> bladernr: that's strange
[18:47] <roaksoax> bladernr: and beta1 goes out today
[18:47] <roaksoax> bladernr: which will have the efi stuff
[18:47] <roaksoax> bladernr: and they have regressed firmware
[18:47] <roaksoax> bladernr: but manufacturesrs say they dont change it
[18:47] <roaksoax> because the ipmi spec has updated as such
[18:48] <bladernr> https://pastebin.ubuntu.com/p/BphvFT6bjW/
[18:48] <bladernr> that's what apt-cache is telling me after updating it
[18:49] <roaksoax> bladernr: ah, you are running xneial ?
[18:50] <bladernr> yeah
[18:50] <roaksoax> bladernr: 2.4 is bionic+
[18:50] <bladernr> ugh...
[18:55] <jac_cplane> MAAS enlists gives sda: unknown partition level.   Any help on how to resolve?
[18:55] <jac_cplane> level=table
[19:48] <mup> Bug #1760191 opened: maas-ipmi-autodetect-tool fails during enlistment for cavium thunder 88xx crb v2 <cdo-qa> <cdo-qa-blocker> <foundations-engine> <MAAS:Incomplete> <https://launchpad.net/bugs/1760191>
[20:03] <mup> Bug #1760191 changed: maas-ipmi-autodetect-tool fails during enlistment for cavium thunder 88xx crb v2 <cdo-qa> <cdo-qa-blocker> <foundations-engine> <MAAS:New> <https://launchpad.net/bugs/1760191>
[20:09] <mup> Bug #1760191 opened: maas-ipmi-autodetect-tool fails during enlistment for cavium thunder 88xx crb v2 <cdo-qa> <cdo-qa-blocker> <foundations-engine> <MAAS:New> <https://launchpad.net/bugs/1760191>