1246236
|
#1246236 |
pxe boot from maas fails due to time out
|
|
MAAS
MAAS
|
2
Critical
|
|
3
Invalid
|
1389811
|
#1389811 |
tgtadm: out of memory crash
|
|
MAAS
MAAS
|
2
Critical
|
|
3
Invalid
|
1395120
|
#1395120 |
MAAS will not import new images if it cannot connect to a cluster controller
|
|
MAAS
MAAS
|
2
Critical
|
|
3
Invalid
|
1395375
|
#1395375 |
Errors logged for failure to shutdown node while not being able to contact cluster
|
|
MAAS
MAAS
|
2
Critical
|
|
3
Invalid
|
1349770
|
#1349770 |
resolv.conf not copied into chroot during curtin install
|
|
MAAS
MAAS
|
3
High
|
|
3
Invalid
|
1367482
|
#1367482 |
virtual nodes don't always PXE boot on the same NIC
|
|
MAAS
MAAS
|
3
High
|
|
3
Invalid
|
1376144
|
#1376144 |
No documentation or lifecycle graph of a node's states
|
|
MAAS
MAAS
|
3
High
|
|
3
Invalid
|
1386482
|
#1386482 |
Bulk actions did not work while node was commissioning
|
|
MAAS
MAAS
|
3
High
|
|
3
Invalid
|
1390097
|
#1390097 |
Suspended and resumed image import seemingly stuck
|
|
MAAS
MAAS
|
3
High
|
|
3
Invalid
|
1390411
|
#1390411 |
No docs on how to take advantage of maas-proxy to cache custom images (e.g. for LXC/KVM containers)
|
|
MAAS
MAAS
|
3
High
|
|
3
Invalid
|
1390094
|
#1390094 |
maas.tftp log spam until images are imported
|
|
MAAS
MAAS
|
4
Medium
|
|
3
Invalid
|
1402124
|
#1402124 |
Bulk commissioning - failure to mount root device from trusty ephemeral image - drops to initramfs shell
|
|
MAAS
MAAS
|
1
Undecided
|
|
3
Invalid
|
1379155
|
#1379155 |
"Boot image import process not started." persists even though I just started an image import which is in progress
|
|
MAAS
MAAS
|
3
High
|
|
4
Won't Fix
|
1379636
|
#1379636 |
pserv "connection refused" errors spamming its log file
|
|
MAAS
MAAS
|
3
High
|
|
4
Won't Fix
|
1390145
|
#1390145 |
There is no timeout for 'Disk Erasing'
|
|
MAAS
MAAS
|
3
High
|
|
4
Won't Fix
|
1272016
|
#1272016 |
Which interface to bind maas-region-controller to should be a debconf question
|
|
MAAS
MAAS
|
4
Medium
|
|
4
Won't Fix
|
1381058
|
#1381058 |
Upgrading introduces a spurious cluster controller
|
|
MAAS
MAAS
|
1
Undecided
|
|
4
Won't Fix
|
1386327
|
#1386327 |
Juju fails to destroy-environment with wipe enabled: Node cannot be released in its current state ('Disk erasing').
|
|
MAAS
MAAS
|
1
Undecided
|
|
4
Won't Fix
|
1389852
|
#1389852 |
Newer Ubuntu images in second boot source not imported
|
|
MAAS
MAAS
|
1
Undecided
|
|
4
Won't Fix
|
1415820
|
#1415820 |
PXE timeout enlisting nodes with MAAS 1.7-rc5
|
|
MAAS
MAAS
|
1
Undecided
|
|
4
Won't Fix
|
1389351
|
#1389351 |
Duplicate eth0 definition
|
|
MAAS
MAAS
|
2
Critical
|
|
10
Fix Released
|
1439359
|
#1439359 |
When upgrading to MAAS 1.7 from MAAS 1.5, MAAS should trigger the image import automatically.
|
|
MAAS
MAAS
|
2
Critical
|
Blake Rouse
|
10
Fix Released
|
1439366
|
#1439366 |
MAAS 1.7 should be backwards compatible with 1.5 the preseed naming convention
|
|
MAAS
MAAS
|
2
Critical
|
Raphaël Badin
|
10
Fix Released
|
1441933
|
#1441933 |
Internal Server Error when saving a cluster without Router IP
|
|
1.7
1.7
|
2
Critical
|
Raphaël Badin
|
10
Fix Released
|
1331214
|
#1331214 |
MAAS (amttool) cannot control AMT version > 8
|
|
1.7
1.7
|
3
High
|
Raphaël Badin
|
10
Fix Released
|
1441133
|
#1441133 |
MAAS version not exposed over the API
|
|
1.7
1.7
|
3
High
|
Raphaël Badin
|
10
Fix Released
|