Ubuntu
maas package

netboot flag defaults to 'true' on upgrade, even for allocated nodes

  1. Precise (12.04)
  2. Bug #1208497
Bug #1208497 reported by James Troup
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Critical
Raphaël Badin
MAAS 13.10 "saucy"
1.2
Fix Released
Critical
Raphaël Badin
1.3
Fix Released
Critical
Raphaël Badin
maas (Ubuntu)
Fix Released
Undecided
Unassigned
Precise
Won't Fix
Undecided
Unassigned
Quantal
Won't Fix
Undecided
Unassigned
Raring
Won't Fix
Undecided
Unassigned

Bug Description

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.

Related branches

lp:~rvb/maas/netboot-allocated
Julian Edwards (community): Approve
Gavin Panella (community): Approve
Diff: 227 lines (+223/-0)
1 file modified
src/maasserver/migrations/0056_netboot_off_for_allocated_nodes.py (+223/-0)
lp:~rvb/maas/netboot-allocated-fix-mig-10
Gavin Panella (community): Approve
Diff: 28 lines (+9/-1)
1 file modified
src/maasserver/migrations/0010_add_node_netboot.py (+9/-1)
lp:~rvb/maas/netboot-allocated-fix-mig-10-1.3
Julian Edwards (community): Approve
Diff: 28 lines (+9/-1)
1 file modified
src/maasserver/migrations/0010_add_node_netboot.py (+9/-1)
lp:~rvb/maas/netboot-allocated-fix-mig-10-1.2
Julian Edwards (community): Approve
Diff: 28 lines (+9/-1)
1 file modified
src/maasserver/migrations/0010_add_node_netboot.py (+9/-1)
Gavin Panella (allenap)
Changed in maas:
status: New → Triaged
importance: Undecided → Critical
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in maas (Ubuntu):
status: New → Confirmed
Julian Edwards (julian-edwards)
Changed in maas:
milestone: none → 13.10
Raphaël Badin (rvb)
Changed in maas:
assignee: nobody → Raphaël Badin (rvb)
status: Triaged → In Progress
Andres Rodriguez (andreserl)
Changed in maas (Ubuntu):
status: Confirmed → Fix Released
Julian Edwards (julian-edwards)
Changed in maas:
status: Fix Committed → Fix Released
Revision history for this message
Rolf Leggewie (r0lf) wrote :

quantal has seen the end of its life and is no longer receiving any updates. Marking the quantal task for this ticket as "Won't Fix".

Changed in maas (Ubuntu Quantal):
status: New → Won't Fix
Revision history for this message
Rolf Leggewie (r0lf) wrote :

raring has seen the end of its life and is no longer receiving any updates. Marking the raring task for this ticket as "Won't Fix".

Changed in maas (Ubuntu Raring):
status: New → Won't Fix
Revision history for this message
Steve Langasek (vorlon) wrote :

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release

Changed in maas (Ubuntu Precise):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.