MAAS

Bugs for 3.5

1 → 17 of 17 results First • Previous • Next • Last
High
Triaged
#2042433 Errors to query/control power are not propagated to the UI
MAAS 3.5 6
High
Triaged
#2036405 cannot unlink subnet after commission
MAAS 3.5 16
High
Triaged
#2062005 Deploys to memory don't configure networking of non-Ubuntu images
MAAS 3.5 6
High
Triaged
#2039614 Update to maas 3.4.0 snap changed partition ids which broke automated deployments
MAAS 3.5 20
High
Triaged
#2009541 MAAS complains about commissioning release during initial setup
MAAS 3.5 6
High
Triaged
#2080646 MAAS_PATH env variable missing from snap env, causes maas not to be able to connect to virsh
MAAS 3.5 6
High
Triaged
#2083076 MAAS nodes that fail commissioning continue to use stale commissioning scripts
MAAS 3.5 26
High
Triaged
#2114240 duplicate "configure-httpproxy-service" workflow
MAAS 3.5 6
High
Triaged
#2114942 MAAS Creates Redfish BMC User Without Sufficient Privileges
MAAS 3.5 12
High
Triaged
#2115797 LXD VM host not always deploys in 3.6
MAAS 3.5 6
High
Triaged
#2125138 Creating a manual dns A record that matches the hostname of an existing machine is going to mess up all the A records for that machine
MAAS 3.5 10
High
Triaged
#2125396 StaticIPAddress auto IP allocation fails because of unhandled exception
MAAS 3.5 6
Medium
Triaged
#2091949 MAAS 3.5.2 does not fully configure network device when doing so in UI
MAAS 3.5 6
Undecided
Triaged
#2058077 MAAS adds custom named.conf.options entry at install, but doesn't remove it at uninstall, breaks bind9
MAAS 3.5 6
Undecided
New
#2078941 When the snap is initialized again the certificates are not cleaned up
MAAS 3.5 6
Undecided
Triaged
#2109708 MAAS RAID size is float, not int, for raid-10
MAAS 3.5 6
Undecided
New
#2116118 MAAS hadware sync unit fails, machines are incorrectly marked as "rebooting" in MAAS
MAAS 3.5 6
1 → 17 of 17 results First • Previous • Next • Last

Series-targeted bugs

Milestone-targeted bugs