| NickW | So, I'm sure many others have asked, but any idea what's going on with CentOS8 support? The current MAAS 2.8 edge snap still has curtin 19.3-26-g82f23e3d-0ubuntu1~18.04.1 which doesn't support it | 02:23 |
|---|---|---|
| NickW | Which basically means that rolling CentOS8 with MAAS is impossible on a 20.04 host, since the maas debs are outdated/won't install | 02:24 |
| mup | Bug #1865844 changed: Add KVM/LXD host id to machine payload in WS API <MAAS:Invalid by ltrager> <https://launchpad.net/bugs/1865844> | 02:25 |
| mup | Bug #1877126 opened: default KVM pod RAM (1GB) is not enough to commission <MAAS:New> <https://launchpad.net/bugs/1877126> | 14:20 |
| mup | Bug #1877140 opened: better UX to validate KVM host addresses <MAAS:New> <https://launchpad.net/bugs/1877140> | 15:44 |
| alejandrosg_ | folks, how can I "rescan" a machine to detect new hardware (added RAM, new disk) in MaaS? | 15:53 |
| mup | Bug #1877158 opened: Static routes in subnet are ignored in multihomed deployments with policy based routing <sts> <MAAS:New> <https://launchpad.net/bugs/1877158> | 17:08 |
| mup | Bug #1877186 opened: pod compose permission denied if /var/lib/virt has r-x disabled for others <cdo-qa> <foundations-engine> <MAAS:New> <https://launchpad.net/bugs/1877186> | 21:03 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!