Question

1

Maas isn't showing Trusty as a deployable Distro

rated 0 times [ 1] [ 0] / answers: 1 / hits: 430 / 1 Year ago, thu, may 18, 2023, 11:07:08

I am running MAAS 1.3.1 on Ubuntu 12.04.3. I added the trusty OS to /etc/maas/import_pxe_files (RELEASES="precise raring trusty"
).

I ran the maas-import-pxe-files script and it seemed to have downloaded Trusty, but I am not seeing it in the as a deployable release. Is there anywhere else I need to set this? or is Trusty downloading as an RC (or something similar) and MAAS isn't willing to deploy it.

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

riffnkful

Add To Favorites

Follow

Total Points: 390

Total Questions: 123

Total Answers: 110

Location: Puerto Rico

Member since Sat, Mar 13, 2021

3 Years ago

answered 1 Year ago teromato · Accepted Answer

To allow later versions of Ubuntu to show up in MAAS <= 1.4 you would need to edit the file /usr/share/pyshared/maasserver/enum.py to add the new release names to the MAAS web UI.

For example, you would need to change the DISTRO_SERIES class as follows:

class DISTRO_SERIES:

    """List of supported ubuntu releases."""

    #:

    default = ''

    #:

    precise = 'precise'

    #:

    quantal = 'quantal'

    #:

    raring = 'raring'

    #:

    saucy = 'saucy'

    #:

    trusty = 'trusty'



DISTRO_SERIES_CHOICES = (

    (DISTRO_SERIES.default, 'Default Ubuntu Release'),

    (DISTRO_SERIES.precise, 'Ubuntu 12.04 LTS "Precise Pangolin"'),

    (DISTRO_SERIES.quantal, 'Ubuntu 12.10 "Quantal Quetzal"'),

    (DISTRO_SERIES.raring, 'Ubuntu 13.04 "Raring Ringtail"'),

    (DISTRO_SERIES.saucy, 'Ubuntu 13.10 "Saucy Salamander"'),

    (DISTRO_SERIES.trusty, 'Ubuntu 14.04 LTS "Trusty Tahr"'),

)

You do have to make sure you have also downloaded the boot images into /var/lib/maas/ephemeral/ so they are available.
But then you should be able to select each version from the MAAS web ui as a deployment target.

If you are using Juju to deploy, then make sure you also update your environments.yaml file's default-series parameter to select the series you want to deploy.