MAAS imports Trusty's 'rc' images by default.

The reason it was made to import both was that upon release, the "rc" images were supposed to be removed. That clearly has not happened, but is the easiest way to fix this bug. This is not an urgent change once that has happened.

rc images were never intended to be removed. nor will 'release' versions in the future.
cloud-images has 'release', 'rc', 'beta' images all available.

the general plan for cloud images has always been to keep *anything* called 'release' indefinitely. We can change that policy for maas images to be "only keep the latest N" or something, but 'N' will most certainly be greater than 1 which will expose the bug.

maas *should* only import the latest 'N' versions. I was told that 'N' was set to '1' for maas. If its not doing that then you need to fix it.

fwiw, bug 1309761 does a much better job of describing the problem.

All this fix in the merge proposal will do is delay the problem until there are 2 images named 'release' with different version numbers on them.

> All this fix in the merge proposal will do is delay the problem until there are 2 images named 'release' with different version
> numbers on them.

The idea is to buy time to SRU a fix to let a user select which image to use when there is a choice.

fwiw, I just now removed the 'rc' items from the metadata.
this will alleviate the immediate issue, but the problem is still critical and would re-show itself as soon as we need to refresh images (which is going to happen with security vulnerability or kernel update).

This is not fixed yet, MAAS needs to select the latest version of the label by default.

This bug was fixed in the package maas - 1.5+bzr2267-0ubuntu1

---------------
maas (1.5+bzr2267-0ubuntu1) utopic; urgency=medium

  * New upstream bugfix release. Fixes:
    - Hardware Enablement for Cisco B-Series. (LP: #1300476)
    - Allow AMT power type to specify IP Address. (LP: #1308772)
    - Spurious failure when starting and creating lock files. (LP: 1308069)
    - Fix regression introduced by a security fix (LP: #1311433, LP: #1311433)
    - Fix usage of hardware enablement kernels by fixing the preseeds
      (LP: #1310082, LP: #1310076, LP: #1310082)
    - Fix parallel juju deployments. (LP: #1314409)
    - Clear distro_series when stopping node from WebUI (LP: #1316396)
    - Fix click hijacking (LP: #1298784)
    - Fix blocking API client when deleting a resource (LP: #1313556)
    - Do not import Trusty RC images by default (LP: #1311151)
 -- Andres Rodriguez <email address hidden> Tue, 15 Apr 2014 14:41:32 -0400

Hello Raphaël, or anyone else affected,

Accepted maas into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/maas/1.5.1+bzr2269-0ubuntu0.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

This bug was fixed in the package maas - 1.5.1+bzr2269-0ubuntu0.1

---------------
maas (1.5.1+bzr2269-0ubuntu0.1) trusty; urgency=medium

  * Stable Release Update (LP: #1317601):
    - Hardware Enablement for Cisco B-Series. (LP: #1300476)
    - Allow AMT power type to specify IP Address. (LP: #1308772)
    - Spurious failure when starting and creating lock files. (LP: 1308069)
    - Fix usage of hardware enablement kernels by fixing the preseeds
      (LP: #1310082, LP: #1310076, LP: #1310082)
    - Fix parallel juju deployments. (LP: #1314409)
    - Clear distro_series when stopping node from WebUI (LP: #1316396)
    - Fix click hijacking (LP: #1298784)
    - Fix blocking API client when deleting a resource (LP: #1313556)
    - Do not import Trusty RC images by default (LP: #1311151)
    - debian/control: Add missing dep on python-crochet for
      python-maas-provisioningserver (LP: #1311765)
 -- Andres Rodriguez <email address hidden> Fri, 09 May 2014 22:35:43 -0500

The verification of the Stable Release Update for maas has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.