[SRU] 14.04 images not available for commissioning as distro-info --lts now reports xenial

Bug #1573046 reported by Andrew McDermott
56
This bug affects 8 people
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Critical
Andres Rodriguez
maas (Ubuntu)
Fix Released
Critical
Unassigned
Trusty
Fix Released
Critical
Unassigned
Wily
Won't Fix
Critical
Unassigned

Bug Description

[Impact]
With the new version of distro-info hitting the archives, and it reporting that the LTS is 16.04, MAAS 1.7, 1.8, 1.9 won't be able to commission machines. This is because MAAS depended on distro-info to determine the commissioning release, which at the time is only Trusty.

[Test Case]
1. install maas
2. go to settings page and select commissioning release.
3. with the fix, trusty will be available. Without the fix, no commissioning will be available and machines will fail to commission/enlist.

[Regression Potential]
Minimal.

[Original bug report]
I re-installed my vMAAS setup from scratch today. I imported 14.04 LTS images but that does not allow me to commission anything - the drop-down in the UI says "No usable Release" for commissioning.

The following conversation should sum up the issue:

frobware> in 1.9.1 I have only 14.04 images, but this gives me "No usable Release" for commissioning. Does it have to be 16.04 only?

<roaksoax> frobware: that's not possible :) because you can't commissioning with xenial in 16.04
<roaksoax> frobware: so maybe the image hasn't finish importting ?
<roaksoax> frobware: you'll need 14.04
<roaksoax> frobware: ohhhhh unless.... this may be an issue with python-distroinfo then
<roaksoax> frobware: wat does distro-info --lts show you?

<frobware> roaksoax: aim@maas19:/var/lib/maas/boot-resources$ distro-info --lts
<frobware> xenial

<roaksoax> frobware: that is in trusty ?
<roaksoax> frobware: is your machine trusty ?

<frobware> yes
<frobware> aim@maas19:/var/lib/maas/boot-resources$ lsb_release -cs
<frobware> trusty

<roaksoax> frobware: can you please file a bug...
<roaksoax> frobware: maas uses distro-info to show what release is LTS
<roaksoax> frobware: so since that is now showing xenial
<roaksoax> frobware: it is not allowing trusty

Related branches

Changed in maas:
importance: Undecided → Critical
milestone: none → 1.9.2
status: New → Confirmed
David Britton (dpb)
tags: added: landscape
tags: added: kanban-cross-team
tags: removed: kanban-cross-team
Changed in maas:
status: Confirmed → In Progress
assignee: nobody → Andres Rodriguez (andreserl)
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
summary: - 14.04 images not available for commissioning as distrio-info --lts now
+ 14.04 images not available for commissioning as distro-info --lts now
reports xenial
Revision history for this message
Andrew McDermott (frobware) wrote : Re: 14.04 images not available for commissioning as distro-info --lts now reports xenial

A workaround to apply on your MAAS instance:

  http://paste.ubuntu.com/15965420/

Revision history for this message
Andres Rodriguez (andreserl) wrote :

The fix has been made available in ppa:maas/stable

Felipe Reyes (freyes)
tags: added: sts
Revision history for this message
Chris Clark (chrclark) wrote :

I found a workaround that worked for me --

edit /usr/share/distro-info/ubuntu.csv

and remove these lines --

15.04,Vivid Vervet,vivid,2014-10-23,2015-04-23,2016-01-23
15.10,Wily Werewolf,wily,2015-04-23,2015-10-22,2016-07-22
16.04 LTS,Xenial Xerus,xenial,2015-10-22,2016-04-21,2021-04-21
16.10,Yakkety Yak,yakkety,2016-04-21,2016-10-20,2017-07-20

BEFORE:
root@bootstrap:/usr/share/distro-info# distro-info --lts
xenial
root@bootstrap:/usr/share/distro-info# vi ubuntu.csv

AFTER
root@bootstrap:/usr/share/distro-info# distro-info --lts
trusty

Revision history for this message
Andres Rodriguez (andreserl) wrote : Re: [Bug 1573046] Re: 14.04 images not available for commissioning as distro-info --lts now reports xenial

Fix is available in ppa:maas/stable or PPA:maas/proposed for 1.9.2

On Thursday, April 28, 2016, Chris Clark <email address hidden> wrote:

> I found a workaround that worked for me --
>
> edit /usr/share/distro-info/ubuntu.csv
>
> and remove these lines --
>
> 15.04,Vivid Vervet,vivid,2014-10-23,2015-04-23,2016-01-23
> 15.10,Wily Werewolf,wily,2015-04-23,2015-10-22,2016-07-22
> 16.04 LTS,Xenial Xerus,xenial,2015-10-22,2016-04-21,2021-04-21
> 16.10,Yakkety Yak,yakkety,2016-04-21,2016-10-20,2017-07-20
>
> BEFORE:
> root@bootstrap:/usr/share/distro-info# distro-info --lts
> xenial
> root@bootstrap:/usr/share/distro-info# vi ubuntu.csv
>
> AFTER
> root@bootstrap:/usr/share/distro-info# distro-info --lts
> trusty
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1573046
>
> Title:
> 14.04 images not available for commissioning as distro-info --lts now
> reports xenial
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1573046/+subscriptions
>

--
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
MSc. Telecom & Networking
Systems Engineer

Revision history for this message
Felipe Reyes (freyes) wrote : Re: 14.04 images not available for commissioning as distro-info --lts now reports xenial

This problem is affecting the version available in trusty-updates (1.7.6+bzr3376-0ubuntu2~14.04.1) and Wily (1.8.3+bzr4053-0ubuntu1), I'll SRU the fix

Changed in maas (Ubuntu):
assignee: nobody → Felipe Reyes (freyes)
Felipe Reyes (freyes)
Changed in maas (Ubuntu Trusty):
assignee: nobody → Felipe Reyes (freyes)
Changed in maas (Ubuntu Wily):
assignee: nobody → Felipe Reyes (freyes)
Changed in maas (Ubuntu):
assignee: Felipe Reyes (freyes) → nobody
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in maas (Ubuntu Trusty):
status: New → Confirmed
Changed in maas (Ubuntu Wily):
status: New → Confirmed
Changed in maas (Ubuntu):
status: New → Confirmed
Revision history for this message
Andres Rodriguez (andreserl) wrote :

Felipe,

Theres currently an SRU *already* in progress.

Revision history for this message
Felipe Reyes (freyes) wrote : Re: [Bug 1573046] Re: 14.04 images not available for commissioning as distro-info --lts now reports xenial

On Sat, 30 Apr 2016 03:43:31 -0000
Andres Rodriguez <email address hidden> wrote:

> Theres currently an SRU *already* in progress.

Great, thanks for the update.

Felipe Reyes (freyes)
Changed in maas (Ubuntu Trusty):
assignee: Felipe Reyes (freyes) → nobody
Changed in maas (Ubuntu Wily):
assignee: Felipe Reyes (freyes) → nobody
Changed in maas (Ubuntu):
assignee: nobody → Andres Rodriguez (andreserl)
Changed in maas (Ubuntu Trusty):
assignee: nobody → Andres Rodriguez (andreserl)
Changed in maas (Ubuntu):
importance: Undecided → Critical
Changed in maas (Ubuntu Wily):
importance: Undecided → Critical
Changed in maas (Ubuntu Trusty):
importance: Undecided → Critical
summary: - 14.04 images not available for commissioning as distro-info --lts now
- reports xenial
+ [SRU] 14.04 images not available for commissioning as distro-info --lts
+ now reports xenial
Changed in maas (Ubuntu):
status: Confirmed → Fix Released
Changed in maas (Ubuntu Wily):
assignee: nobody → Andres Rodriguez (andreserl)
Changed in maas (Ubuntu):
assignee: Andres Rodriguez (andreserl) → nobody
Changed in maas (Ubuntu Trusty):
milestone: none → trusty-updates
Changed in maas (Ubuntu Wily):
milestone: none → wily-updates
Changed in maas (Ubuntu Trusty):
assignee: Andres Rodriguez (andreserl) → nobody
Changed in maas (Ubuntu Wily):
assignee: Andres Rodriguez (andreserl) → nobody
description: updated
description: updated
Revision history for this message
Steve Langasek (vorlon) wrote : Please test proposed package

Hello Andrew, or anyone else affected,

Accepted maas into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/maas/1.7.6+bzr3376-0ubuntu3~14.04.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!

Changed in maas (Ubuntu Trusty):
status: Confirmed → Fix Committed
tags: added: verification-needed
Changed in maas (Ubuntu Wily):
status: Confirmed → Fix Committed
Revision history for this message
Steve Langasek (vorlon) wrote :

Hello Andrew, or anyone else affected,

Accepted maas into wily-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/maas/1.8.3+bzr4053-0ubuntu2~15.10.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!

Revision history for this message
Felipe Reyes (freyes) wrote :

I can commission nodes with trusty using the package from -proposed

Evidence: screenshot while commissioning node

with maas from -updates: http://people.canonical.com/~freyes/lp1573046-from-updates.png
with maas from -proposed: http://people.canonical.com/~freyes/lp1573046-from-proposed.png

tags: added: verification-done
removed: verification-needed
Revision history for this message
Martin Pitt (pitti) wrote : Update Released

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 regressions.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package maas - 1.7.6+bzr3376-0ubuntu3~14.04.1

---------------
maas (1.7.6+bzr3376-0ubuntu3~14.04.1) trusty-proposed; urgency=medium

  * debian/patches/lp1573046.patch: No longer use distro-info --lts to
    detect the commissioning release, as it returns 'xenial' for LTS.
    MAAS 1.7 only supports trusty. (LP: #1573046)

 -- Andres Rodriguez <email address hidden> Mon, 09 May 2016 16:29:28 -0400

Changed in maas (Ubuntu Trusty):
status: Fix Committed → Fix Released
Revision history for this message
Martin Pitt (pitti) wrote :

This was apparently verified for trusty, but not for wily.

tags: added: verification-done-trusty verification-needed
removed: verification-done
Revision history for this message
Martin Pitt (pitti) wrote :

The wily update was not verified in three months, and wily is almost EOL. So I removed the -proposed package.

Changed in maas (Ubuntu Wily):
status: Fix Committed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.