=== mup_ is now known as mup
=== jnsgruk08 is now known as jnsgruk0
[09:18] <CANqVH> Heyo, currently changed IP addres of vm whre i have installed maas(region+rack) (2.9.2 (9164-g.ac176b5c4-0ubuntu1~20.04.1)), after IP change (vm+maas controller) acing problem on deployed machines, e.g couldn't "apt-get update" cuz machine is looking for old IP....after removing /etc/apt/apt.conf.d/90curtin-aptproxy it is ok :D but wondering if there is any other dependency or how to chagne IP the rigt way ?
[09:24] <CANqVH> ok, my bad, probably better to change to new IP proxy in /etc/apt/apt.conf.d/90curtin-aptproxy
=== greenstatic3 is now known as greenstatic
=== shann_ is now known as shann
[18:13] <mup> Bug #1918713 opened: Composing a LXD VM with multiple interfaces doesn't work <ui> <MAAS:New> <https://launchpad.net/bugs/1918713>
[18:19] <mup> Bug #1918713 changed: Composing a LXD VM with multiple interfaces doesn't work <ui> <MAAS:New> <maas-ui:New> <https://launchpad.net/bugs/1918713>
[18:25] <mup> Bug #1918713 opened: Composing a LXD VM with multiple interfaces doesn't work <ui> <MAAS:New> <maas-ui:New> <https://launchpad.net/bugs/1918713>
[20:04] <mup> Bug #1918481 changed: MAAS doesn't support thin LVM2 partitioning. <lvm2> <partitioning> <redhat> <thin> <virtualization> <MAAS:Invalid> <https://launchpad.net/bugs/1918481>
[20:10] <mup> Bug #1918481 opened: MAAS doesn't support thin LVM2 partitioning. <lvm2> <partitioning> <redhat> <thin> <virtualization> <MAAS:Invalid> <https://launchpad.net/bugs/1918481>
[20:13] <mup> Bug #1918481 changed: MAAS doesn't support thin LVM2 partitioning. <lvm2> <partitioning> <redhat> <thin> <virtualization> <MAAS:Invalid> <https://launchpad.net/bugs/1918481>
[20:49] <mup> Bug #1918481 opened: MAAS doesn't support thin LVM2 partitioning. <lvm2> <partitioning> <redhat> <thin> <virtualization> <MAAS:New> <https://launchpad.net/bugs/1918481>