Can't use both daily and released images in the same MAAS

[Jason Hobbs]

I have a MAAS I usually run release images on, but I want to test if the latest daily image fixes an issue I'm having with one system. I'd like the other systems to continue using the release version of the images.

I can't do this today, because MAAS only supports using either the daily or the release version of images.

[Blake Rouse (blake-rouse)]

You actual can do this today, but not using the UI. That is a very specific case and we support it over the API.

Once you have both boot-sources add over the API, setup the selections to only include the series you want for releases and the series you want for daily.

Example (utopic on daily, rest on releases)

BootSource ID 1: releases
BootSource ID 2: daily

Make sure all current selections are deleted.

maas admin boot-source-selections create 1 os="ubuntu" release="precise" arches="amd64" arches="arm64" subarches="*" labels="*"
maas admin boot-source-selections create 1 os="ubuntu" release="trusty" arches="amd64" arches="arm64" subarches="*" labels="*"
maas admin boot-source-selections create 2 os="ubuntu" release="utopic" arches="amd64" arches="arm64" subarches="*"
labels="*"

To the example I added arm64 so you can see how to setup multiple arches in a selection. This will enable what you are requesting.

Supporting this ability in the Image UI will most likely not happen as it will make the UI overly complex, when only a few users need that feature.

[Jason Hobbs (jason-hobbs)]

I want to be able to use trusty daily and trusty release on the same MAAS - not separate distro_releases.

[Blake Rouse (blake-rouse)]

Miss understood. Thanks for clarifying.

[Ryan Beisner (1chb1n)]

+1 to this a feature request and enhancement for MAAS.

In some cases, it is desirable to use daily images for some releases, while using released images for other releases.

Scenario A:
User wishes to deploy or test the current Ubuntu Server development release by enabling daily images (Xenial at this time).

To achieve that, it is necessary to enable daily images, which enables dailies for all releases.

That user, or another user in the same MAAS lab wishes to deploy released image of an LTS (Trusty at this time), but will only be able to deploy that LTS's daily image.

...

Scenario B:
CI automation needs to deploy and exercise the dev release (Xenial), and can only do so by enabling daily images.

CI automation needs to deploy and exercise other currently-supported releases (Trusty, Wily), and is forced to do so with daily images, due to the previous statement.

A daily maas image happens to break in some way for non-dev release (Trusty), making that non-dev release untestable until a new daily image fixes the issue.

CI operations for that version halt in that lab. If the CI operator switches the lab to released images to resume operations, the ability to test the dev release is lost.

[Ryan Beisner (1chb1n)]

So I see that my two scenarios are doable via API. Convert to web UI feature request. :-) Please & thanks.

[Andres Rodriguez (andreserl)]

Hi!

**This is an automated message**

We believe this is may no longer be an issue in the latest MAAS release. Due to the date of this bug report, we are marking this bug report as invalid. If you believe this is still an issue, please re-open this bug report.

Thanks