/srv/irclogs.ubuntu.com/2020/03/26/#maas.txt

mupBug #1869116 opened: smartctl-validate is borked in a recent release <MAAS:New> <https://launchpad.net/bugs/1869116>01:35
tosarajaltrager: wow, ok thanks. So this is a matter of firmware on the NIC? In which case I could try the on board 1GB links for booting and then the 10GB links for data transfer once we're up? I mean I could test if that works05:56
=== parlos is now known as parlos_afk
=== parlos_afk is now known as parlos
mupBug #1867222 changed: MAAS should support hostnames for BMC addresses <MAAS:Invalid> <https://launchpad.net/bugs/1867222>09:57
mupBug #1867222 opened: MAAS should support hostnames for BMC addresses <MAAS:Invalid> <https://launchpad.net/bugs/1867222>10:00
mupBug #1867222 changed: MAAS should support hostnames for BMC addresses <MAAS:Invalid> <https://launchpad.net/bugs/1867222>10:06
=== parlos is now known as parlos_afk
=== parlos_afk is now known as parlos
=== parlos is now known as parlos_afk
=== parlos_afk is now known as parlos
=== parlos is now known as parlos_afk
=== parlos_afk is now known as parlos
=== parlos is now known as parlos_afk
mupBug #1866118 changed: 2.6.2 new nodes always are calculated as ephemeral deploys <MAAS:New> <https://launchpad.net/bugs/1866118>12:09
mupBug #1866118 opened: 2.6.2 new nodes always are calculated as ephemeral deploys <MAAS:New> <https://launchpad.net/bugs/1866118>12:15
mupBug #1866118 changed: 2.6.2 new nodes always are calculated as ephemeral deploys <MAAS:New> <https://launchpad.net/bugs/1866118>12:21
=== parlos_afk is now known as parlos
mupBug #1867991 opened: Commissioning fails due to linux-modules package when using 20.04 for commissioning  <hwcert-server> <MAAS:New> <maas-images:Invalid> <https://launchpad.net/bugs/1867991>13:45
mupBug #1867991 changed: Commissioning fails due to linux-modules package when using 20.04 for commissioning  <hwcert-server> <MAAS:New> <maas-images:Invalid> <https://launchpad.net/bugs/1867991>13:51
mupBug #1867991 opened: Commissioning fails due to linux-modules package when using 20.04 for commissioning  <hwcert-server> <MAAS:New> <maas-images:Invalid> <https://launchpad.net/bugs/1867991>13:54
=== parlos is now known as parlos_afk
mupBug #1867991 changed: Commissioning fails due to linux-modules package when using 20.04 for commissioning  <hwcert-server> <MAAS:New> <maas-images:Invalid> <https://launchpad.net/bugs/1867991>14:12
=== parlos_afk is now known as parlos
=== parlos is now known as parlos_afk
=== parlos_afk is now known as parlos
=== parlos is now known as parlos_afk
=== parlos_afk is now known as parlos
=== parlos is now known as parlos_afk
=== parlos_afk is now known as parlos
=== parlos is now known as parlos_afk
=== parlos_afk is now known as parlos
mupBug #1869264 opened: Upgrade from MAAS 2.6.0 to 2.6.2 in HA environment results in maas DB user's password reset, no MAAS nodes able to connect to DB <MAAS:New> <https://launchpad.net/bugs/1869264>21:28
mupBug #1869264 changed: Upgrade from MAAS 2.6.0 to 2.6.2 in HA environment results in maas DB user's password reset, no MAAS nodes able to connect to DB <MAAS:New> <https://launchpad.net/bugs/1869264>21:31
mupBug #1869264 opened: Upgrade from MAAS 2.6.0 to 2.6.2 in HA environment results in maas DB user's password reset, no MAAS nodes able to connect to DB <MAAS:New> <https://launchpad.net/bugs/1869264>21:34
mupBug #1869264 changed: Upgrade from MAAS 2.6.0 to 2.6.2 in HA environment results in maas DB user's password reset, no MAAS nodes able to connect to DB <MAAS:New> <https://launchpad.net/bugs/1869264>21:37
mupBug #1869264 opened: Upgrade from MAAS 2.6.0 to 2.6.2 in HA environment results in maas DB user's password reset, no MAAS nodes able to connect to DB <MAAS:New> <https://launchpad.net/bugs/1869264>21:43
mupBug #1869269 opened: UI Stuck on loading <MAAS:New> <https://launchpad.net/bugs/1869269>22:25

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!