[precise] MAAS warns about missing ISOs even after they've been processed

Bug #1003460 reported by Mike
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Unassigned

Bug Description

When the system is installed, opening the MAAS dashboard URL provides a message with a yellow background:
 "Some of the required system profiles are missing. Run the maas-import-isos script to import Ubuntu isos and create the related profiles:
 sudo maas-import-isos"

However, even after running the above process and confirming that everything completed, that warning message remains. The message remained until I began commissioing nodes, at which point it was replaced with the "Commissioning Nodes" message.

The message should have gone away once maas-import-isos had completed - even if I needed to refresh the page to make it update - which I tried but it didn't.

Revision history for this message
Raphaël Badin (rvb) wrote :

We store this information (whether or not the script maas-import-isos needs to be run) in a value that is cached using Django's cache. However, we're using a cache local to each thread (see CACHES in src/maas/settings.py) so the script maas-import-isos does not clear the WSGI application's cache (it calls "maas clearcache --key=profile-check-done").

A proper fix would be to use a shared cache using memcache.

An easy workaround is to reduce PROFILE_CHECK_DELAY in src/maasserver/middleware.py to a few seconds.

Changed in maas:
status: New → Triaged
importance: Undecided → High
Raphaël Badin (rvb)
affects: maas → maas (Ubuntu)
affects: maas (Ubuntu) → maas
Revision history for this message
Kodamati Pradeep Vinesh Reddy (pradeep-reddy2) wrote :

Due to this error I am not able to accept and commission the nodes that I am trying to add.

Revision history for this message
Dominic Dunlop (dominic-dunlop) wrote :

I too was stymied by this bug at the Add node stage. Rebooting the server cleared it.

Revision history for this message
Mike (bild85) wrote :

I confirm that rebooting the MAAS server clears this message too

Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

We fixed this in Quantal by storing the component error states centrally in the database.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

The Quantal code may get backported to Precise, we're waiting on various peoples' decisions.

summary: - MAAS warns about missing ISOs even after they've been processed
+ [precise] MAAS warns about missing ISOs even after they've been
+ processed
Revision history for this message
Julian Edwards (julian-edwards) wrote :

The precise backport is now complete, so I'm marking this fix-released.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

I mean SRU not backport.

Changed in maas:
status: Triaged → 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.