Public bug reported:
We recently upgraded our MAAS from 0.1+bzr482+dfsg-0ubuntu1 to
1.2+bzr1373+dfsg-0ubuntu1~12.04.1.
After doing this, we found that MAAS was trying (and thankfully
failing) to reinstall any node we rebooted. This appears be to
because the 'netboot' field which was add to the 'maasserver_node'
table is defaulted to true by migrations/0010_add_node_netboot.py.
This causes get_boot_purpose() in api.py to return 'install' rather
than 'local' for allocated nodes.
I think 'netboot' should be set to false for allocated nodes during
migrations instead.
** Affects: maas
Importance: Critical
Status: Triaged
** Affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1208497
Title:
netboot flag defaults to 'true' on upgrade, even for allocated nodes
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1208497/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
