[00:05] Bug #1892983 opened: ipmi_test crashes when ipmi_config output is not utf-8 [07:31] Bug #1979039 opened: TLS certificates are not recognised by CLI maas boot-resources create action [07:34] Bug #1979039 changed: TLS certificates are not recognised by CLI maas boot-resources create action [07:37] Bug #1979039 opened: TLS certificates are not recognised by CLI maas boot-resources create action [09:46] Bug #1979046 opened: [3.2-rc1] focal is not a valid commissioning distro series [09:49] Bug #1979046 changed: [3.2-rc1] focal is not a valid commissioning distro series [09:52] Bug #1979046 opened: [3.2-rc1] focal is not a valid commissioning distro series [11:38] Hi There, I am struggling with mutliple gateways in multiple subnets. [11:39] The root problem is, that the gateway of MAAS network in my fabric shall only be considered during deployment but after that, the gateway of a different network must be used [11:39] I see that source routing is employed but that does not cut it. [11:40] I thought that removing the MAAS network's default gateway would help, but the other network seems to be set up too late in the process [11:40] Next idea was: add a static route to 0.0.0.0/0 via MAAS gateway with a high metric, but MAAS only allows static routes to subnets that are defined within MAAS [11:40] and MAAS refuses to let me create a subnet with '0.0.0.0/0' [11:46] Question: Is it the right way to suggest to be able to create arbitrary routes, or suggest to model the "world cidr" in MAAS subnets, or something completely different/ [12:34] Bug #1979058 opened: [docs] "space" option still exists as available on Subnet API while being deprecated [12:47] Bug #1979058 changed: [docs] "space" option still exists as available on Subnet API while being deprecated [12:53] Bug #1979058 opened: [docs] "space" option still exists as available on Subnet API while being deprecated [16:20] Bug #1979078 opened: reboot failed with centos8 deployed image