[2.0a1] No usable release for commissioning

Bug #1553590 reported by Mark Shuttleworth
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Undecided
Unassigned

Bug Description

After importing images in MAAS 2.0a1 I still see "No Usable Release" for commissioning, and "No Usable Operating System" for deployment, in the global settings page.

Revision history for this message
Chris Gregan (cgregan) wrote :

Confirmed this issue also exists on 2.0a2

Changed in maas:
milestone: none → 2.0.0
Changed in maas:
status: New → Fix Committed
Revision history for this message
Enrique Chirivella Pérez (echirivella) wrote :

I have the same problem with version "1.9.0+bzr4533-0ubuntu1 (wily1)"

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

@Enrique,

please upgrade to the latest version of 1.9, which includes the fix for the issue you are coming across.

Revision history for this message
Ike Panhc (ikepanhc) wrote :

I try ppa:maas/stable and ppa:maas/proposed, install 2.0.0 (rc2+bzr5156) on Xenial and 1.9.4+bzr4592-0ubuntu1 (trusty1) on Trusty. Can not select OS/Release for deploy/commissioning after LTS images downloaded

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

Hi Ike,

If you cannot select OS/Release for deploy/commission, that means that the download processes has not downloaded all the required files. See /var/log/maas/clusterd.log. It is either due to proxy not being able to access the archive, or no loop devices on your system, preventing the mounting of the image.

Revision history for this message
Ike Panhc (ikepanhc) wrote :

Thanks Andres,

Now I am using 1.9.3+bzr4577-0ubuntu1 (trusty1) and it works properly.

Changed in maas:
status: Fix Committed → Fix Released
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.