| mup | Bug #1703406 changed: MAAS fails to detect Huawei-based server's power type <MAAS:Incomplete> <https://launchpad.net/bugs/1703406> | 04:54 |
|---|---|---|
| zeestrat | Ahoy, what's the recommended upgrade approach from 2.1 to 2.2 when you have 2 region controllers in HA and a couple of rack controllers? I don't see anything on https://docs.ubuntu.com/maas/2.2/en/manage-ha | 07:18 |
| zeestrat | Any specific order things should be upgraded in? | 07:19 |
| mup | Bug #1703535 opened: power error on some servers with status "new" <dell> <ipmi> <power> <MAAS:New> <https://launchpad.net/bugs/1703535> | 07:33 |
| === frankban|afk is now known as frankban | ||
| mwe11 | according to the bug https://launchpad.net/bugs/1703535 : Is it possible to include it into the official release? From my point of view it's not a feature request but a bug report. I spent a couple of hours to fix it in my environment :-( | 07:37 |
| mup | Bug #1703535 opened: power error on some servers with status "new" <dell> <ipmi> <power> <MAAS:New> <maas (Ubuntu):New> <https://launchpad.net/bugs/1703535> | 08:03 |
| kklimonda | it seems there is no network integration for virsh pods, is it planned for 2.3+ ? | 10:00 |
| roaksoax | kklimonda: not for 2.3 | 12:24 |
| mup | Bug #1274527 changed: MAAS doesn't put its DNS server in resolv.conf <micro-cluster> <MAAS:Invalid> <maas (Ubuntu):Invalid> <https://launchpad.net/bugs/1274527> | 12:36 |
| mup | Bug #1703535 changed: power error on some servers with status "new" <dell> <ipmi> <power> <MAAS:Triaged by andreserl> <MAAS 2.2:Triaged> <https://launchpad.net/bugs/1703535> | 12:36 |
| mup | Bug #1703535 changed: power error on some servers with status "new" <dell> <ipmi> <power> <MAAS:Triaged by andreserl> <MAAS 2.2:Triaged> <https://launchpad.net/bugs/1703535> | 12:37 |
| gimmic | I had to increase the backoff wait times on IPMI while using idrac7 on r620's | 14:49 |
| gimmic | otherwise the power commands fail when using the shared LOM | 14:49 |
| gimmic | if using the dedicated drac, it is faster, but using the shared NIC1, it is slower | 14:49 |
| dannf | roaksoax: we have a freeipmi in x,y,z-proposed to fix bmc detection on some arm64 systems. i've tested it on one x86 server and found no regressions. Is there a way to enable it in MAAS CI for a run for larger coverage? | 15:17 |
| * dannf wonders if that's a q for cgregan | 15:18 | |
| * D4RKS1D3 hi! | 15:51 | |
| mup | Bug #1664822 opened: [2.2] MAAS IPMI autodiscover should enable IPMI-over-LAN if disabled <MAAS:In Progress by andreserl> <maas (Ubuntu):New> <https://launchpad.net/bugs/1664822> | 16:00 |
| roaksoax | dannf: is it in xenial-proposed ? | 16:40 |
| dannf | roaksoax: yeah | 16:43 |
| === frankban is now known as frankban|afk | ||
| mup | Bug #1703661 opened: No ability to update MAAS configuration to match updates made on node for future re-deployment <canonical-bootstack> <MAAS:New> <https://launchpad.net/bugs/1703661> | 18:31 |
| mup | Bug #1690781 changed: Compose machine failure: Start tag expected, '<' not found, line 1, column 1 <MAAS:Fix Released by newell-jensen> <https://launchpad.net/bugs/1690781> | 19:01 |
| mup | Bug #1693644 changed: Enlistment does not validate min_hwe_kernel <MAAS:Fix Released by ltrager> <https://launchpad.net/bugs/1693644> | 19:01 |
| mup | Bug #1690781 opened: Compose machine failure: Start tag expected, '<' not found, line 1, column 1 <MAAS:Fix Released by newell-jensen> <https://launchpad.net/bugs/1690781> | 19:04 |
| mup | Bug #1693644 opened: Enlistment does not validate min_hwe_kernel <MAAS:Fix Released by ltrager> <https://launchpad.net/bugs/1693644> | 19:04 |
| mup | Bug #1690781 changed: Compose machine failure: Start tag expected, '<' not found, line 1, column 1 <MAAS:Fix Released by newell-jensen> <https://launchpad.net/bugs/1690781> | 19:13 |
| mup | Bug #1693644 changed: Enlistment does not validate min_hwe_kernel <MAAS:Fix Released by ltrager> <https://launchpad.net/bugs/1693644> | 19:13 |
| gimmic | Is there a reason we can't edit storage while a node is marked as broken? | 19:16 |
| roaksoax | tai/win 3 | 19:19 |
| rfolco | Hi, can MAAS add/commission/deploy LXC containers as nodes, or just VMs ? In https://docs.ubuntu.com/maas/2.1/en/installconfig-install, it suggests local containers can emulate real servers: "MAAS nodes also run as local containers". | 19:34 |
| roaksoax | rfolco: no it can't | 19:44 |
| roaksoax | rfolco: you can run MAAS inside a container | 19:44 |
| rfolco | roaksoax, and from inside that container it manages kvm guests as nodes, right? Can I add kvm guests from outside that container ? | 19:52 |
| rfolco | vlan maybe? | 19:52 |
| roaksoax | rfolco: yes, you can actually add a machine that has lkvm/libvirt in it, as a pod, and MAAS could create VM's on the fly | 20:07 |
| roaksoax | rfolco: the limitation is that networking is not yet sully supported | 20:08 |
| rfolco | roaksoax, thanks. I'll give it a try. | 20:09 |
| mup | Bug #1703671 opened: MaaS unable to power on Intel S2600 servers via IPMI, ipmipower command works fine <MAAS:New> <https://launchpad.net/bugs/1703671> | 20:10 |
| mup | Bug #1657577 changed: [UI] 2.1.3: Dashboard page crashes <oil> <MAAS:Triaged> <https://launchpad.net/bugs/1657577> | 20:37 |
| mup | Bug #1703673 opened: Device discovery page is enormous, takes a long time to load <ux> <MAAS:Triaged> <https://launchpad.net/bugs/1703673> | 21:01 |
| xygnal_ | how do i set boot device automatically, when i can only modify it in ready state? | 21:39 |
| xygnal_ | too early for commission, too late for deploy | 21:39 |
| mup | Bug #1703686 opened: Rack Controller disconnection <registration> <MAAS:Triaged> <MAAS 2.2:Triaged> <https://launchpad.net/bugs/1703686> | 21:40 |
| mpontillo | xygnal_: I didn | 21:47 |
| xygnal_ | didnt what? | 21:47 |
| mpontillo | xygnal_: *didn't think you could set the boot device; MAAS just records whichever interface it last saw booting from the network. we don't really have control over which interface decides to do that | 21:47 |
| mpontillo | (sorry, fat fingers) | 21:48 |
| xygnal_ | not network. disk. | 21:48 |
| mpontillo | xygnal_: ah, that I'm not sure about off the top of my head. blake_r would know (but I think he's sick today) | 21:48 |
| mpontillo | xygnal_: but again I would wonder about the BIOS boot order and whether or not we can change that | 21:49 |
| xygnal_ | its the boot and root i am setting | 21:53 |
| xygnal_ | i think only root needs ready state | 21:53 |
| xygnal_ | sda is NOT out root disk | 21:53 |
| xygnal_ | our | 21:54 |
| mup | Bug #1703671 changed: MaaS unable to power on Intel S2600 servers via IPMI, ipmipower command works fine <ipmi> <MAAS:New> <https://launchpad.net/bugs/1703671> | 22:10 |
| mup | Bug #1703689 opened: [2.2.1] When deploying servers with VLAN using IPv6 alias ifdown fails with cannot find device <curtin:New> <MAAS:Incomplete> <https://launchpad.net/bugs/1703689> | 22:10 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!