Activity log for bug #1316396

Date Who What changed Old value New value Message
2014-05-06 03:50:11 Julian Edwards bug added bug
2014-05-06 03:50:19 Julian Edwards maas: status New Triaged
2014-05-06 03:50:23 Julian Edwards maas: importance Undecided Critical
2014-05-06 03:50:25 Julian Edwards maas: assignee Julian Edwards (julian-edwards)
2014-05-06 03:50:30 Julian Edwards nominated for series maas/1.5
2014-05-06 03:50:30 Julian Edwards bug task added maas/1.5
2014-05-06 03:50:36 Julian Edwards maas/1.5: status New Triaged
2014-05-06 03:50:37 Julian Edwards maas/1.5: importance Undecided Critical
2014-05-06 03:50:40 Julian Edwards maas/1.5: assignee Julian Edwards (julian-edwards)
2014-05-06 04:37:58 Julian Edwards summary When stopping a node from the web UI, distro_series is not cleared When stopping a node from the web UI that was started from the API, distro_series is not cleared
2014-05-06 04:38:49 Julian Edwards description I'm not sure how I got into this state, but one of my nodes that's unallocated has a valid value in its distro_series field. This means that when you start it up from the web UI next time it will now ignore the global default and always use that series because of the logic in Node.get_distro_series(). At the very least, Node.release() should call set_distro_series(series=''). For some odd reason, this is only called from the API release() method rather than the common Node method. I'm not sure how I got into this state, but one of my nodes that's unallocated has a valid value in its distro_series field. This means that when you start it up from the web UI next time it will now ignore the global default and always use that series because of the logic in Node.get_distro_series(). At the very least, Node.release() should call set_distro_series(series=''). For some odd reason, this is only called from the API release() method rather than the common Node method. UPDATE: It had been originally started with the API (which sets the passed distro series) but released with the web UI.
2014-05-06 06:37:32 Launchpad Janitor branch linked lp:~julian-edwards/maas/clear-distroseries-bug-1316396
2014-05-07 02:44:19 MAAS Lander maas: status Triaged Fix Committed
2014-05-07 02:54:11 Launchpad Janitor branch linked lp:~julian-edwards/maas/1.5-clear-distroseries-bug-1316396
2014-05-07 03:03:37 MAAS Lander maas/1.5: status Triaged Fix Committed
2014-05-08 06:22:22 Julian Edwards maas/1.5: milestone 1.5.1
2014-05-08 17:08:09 Launchpad Janitor branch linked lp:~ubuntu-branches/ubuntu/utopic/maas/utopic-proposed
2014-05-08 17:33:09 Andres Rodriguez description I'm not sure how I got into this state, but one of my nodes that's unallocated has a valid value in its distro_series field. This means that when you start it up from the web UI next time it will now ignore the global default and always use that series because of the logic in Node.get_distro_series(). At the very least, Node.release() should call set_distro_series(series=''). For some odd reason, this is only called from the API release() method rather than the common Node method. UPDATE: It had been originally started with the API (which sets the passed distro series) but released with the web UI. [Test Case] 1. Install MAAS 2. Add a node. 3. Deploy the node 4. When you destroy a node, distro_series will remain with the selected distro_series. With the fix: 4. When you destroy a node, distro_series will be cleared. I'm not sure how I got into this state, but one of my nodes that's unallocated has a valid value in its distro_series field. This means that when you start it up from the web UI next time it will now ignore the global default and always use that series because of the logic in Node.get_distro_series(). At the very least, Node.release() should call set_distro_series(series=''). For some odd reason, this is only called from the API release() method rather than the common Node method. UPDATE: It had been originally started with the API (which sets the passed distro series) but released with the web UI.
2014-05-09 02:50:09 Julian Edwards maas/1.5: status Fix Committed Fix Released
2014-05-09 02:50:11 Julian Edwards maas: status Fix Committed Fix Released
2014-05-09 19:55:21 Chris J Arges bug task added maas (Ubuntu)
2014-05-09 19:55:38 Chris J Arges nominated for series Ubuntu Trusty
2014-05-09 19:55:38 Chris J Arges bug task added maas (Ubuntu Trusty)
2014-05-09 19:55:55 Chris J Arges maas (Ubuntu): status New Fix Released
2014-05-10 19:43:07 Nobuto Murata bug added subscriber Nobuto MURATA
2014-05-11 03:22:21 Chris J Arges maas (Ubuntu Trusty): status New Fix Committed
2014-05-11 03:22:23 Chris J Arges bug added subscriber Ubuntu Stable Release Updates Team
2014-05-11 03:22:25 Chris J Arges bug added subscriber SRU Verification
2014-05-11 03:22:34 Chris J Arges tags verification-needed
2014-05-11 03:41:39 Launchpad Janitor branch linked lp:ubuntu/trusty-proposed/maas
2014-05-21 19:44:47 Andres Rodriguez tags verification-needed verification-done
2014-05-21 20:43:08 Launchpad Janitor maas (Ubuntu Trusty): status Fix Committed Fix Released
2014-05-21 20:44:11 Chris J Arges removed subscriber Ubuntu Stable Release Updates Team