MAAS 1.9 CentOS image names and Juju streams disagree

Bug #1507359 reported by John George on 2015-10-18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Lee Trager

Bug Description

MAAS 1.9 can import centos images when 'Boot Images' is set to ''. However, juju can not deploy these images since the name assigned by MAAS does not match the name in the Juju tools stream.

jenkins@finfolk:~$ maas env19 boot-resources read | grep name
        "name": "centos/centos66",
        "name": "centos/centos70",
        "name": "ubuntu/trusty",
        "name": "ubuntu/trusty",
        "name": "ubuntu/trusty",
        "name": "ubuntu/trusty",
        "name": "ubuntu/trusty",
        "name": "ubuntu/trusty",

Juju expects 'centos7' which can be seen at the following URL:

Reproduce as follows:
    1. With MAAS 1.9 (storage set to "flat layout; bug 1499558)
    2. Set 'Boot Images' to ''
    3. Bootstrap with a Juju 1.24.7 client (required to avoid bug 1494476)
    4. juju add-machine --series centos7

This issue can be worked around by re-adding the centos images downloaded by MAAS, as a custom image.
Image location: /var/lib/maas/boot-resources/current/centos/amd64/generic/centos70/release/root-tgz

      'maas <profile-name> boot-resources create title=centos7 name=centos7 architecture=amd64/generic content@=root-tgz'

The error message reported by MAAS when requesting 'centos7' can be seen in the juju status machine output:
    agent-state-info: 'gomaasapi: got error back from server: 400 BAD REQUEST ({"distro_series":
      ["''centos7'' is not a valid distro_series. It should be one of: '''', ''centos/centos66'',
      ''centos/centos70'', ''ubuntu/trusty''."]})'
    instance-id: pending
    series: centos7

Trying to pass 'add-machine' --series centos70 will result is an error that can be seen in Juju's machine logs:
machine-0: 2015-10-18 17:58:08 ERROR juju.worker runner.go:223 exited "environ-provisioner": failed to process updated machines: invalid series "centos70"

Related branches

John George (jog) wrote :
John George (jog) wrote :
Andres Rodriguez (andreserl) wrote :

Hi all,

So I think in MAAS we can easily assume that if centos7/centos8 is specified by Juju, it means centos70 internally. However, provided that other centos releases are 65, 66, etc. should we also assume centos would be 70, 80 across the board?

Changed in maas:
milestone: none → 1.9.0
status: New → Opinion
status: Opinion → Triaged
importance: Undecided → High
Changed in maas:
importance: High → Critical
John George (jog) on 2015-10-21
summary: - MAAS 1.9 image names and Juju streams disagree
+ MAAS 1.9 CentOS image names and Juju streams disagree
Lee Trager (ltrager) on 2015-10-23
Changed in maas:
assignee: nobody → Lee Trager (ltrager)
status: Triaged → In Progress
Changed in maas:
status: In Progress → Fix Committed
Curtis Hovey (sinzui) on 2015-10-28
Changed in juju-core:
importance: Critical → High
Lee Trager (ltrager) on 2015-10-29
Changed in maas-images:
status: New → Invalid
Changed in maas:
status: Fix Committed → Fix Released
tags: added: simplestreams
Changed in juju:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.1.0
no longer affects: juju-core
no longer affects: juju-core/1.24
Anastasia (anastasia-macmood) wrote :

Removing 2.1 milestone as we will not be addressing this issue in 2.1.

Changed in juju:
milestone: 2.1.0 → none
Curtis Hovey (sinzui) on 2017-02-14
Changed in juju:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers