** Changed in: maas
Milestone: 14.10 => None
** Changed in: maas/1.5
Status: Fix Committed => Fix Released
** Changed in: maas
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maa
** Changed in: maas/1.5
Milestone: None => 14.04
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1301809
Title:
Report boot images no directory traceback
To manage notifications ab
** Changed in: maas/1.5
Milestone: 14.04 => None
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1301809
Title:
Report boot images no directory traceback
To manage notifications ab
** Changed in: maas (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1301809
Title:
Report boot images no directory traceback
To manage notifica
** Changed in: maas/1.5
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1301809
Title:
Report boot images no directory traceback
To manage notificat
** Branch linked: lp:~rvb/maas/reporting-bug-1301809-1.5
** Changed in: maas/1.5
Assignee: (unassigned) => Raphaël Badin (rvb)
** Changed in: maas
Status: In Progress => Fix Committed
** Changed in: maas/1.5
Importance: Undecided => Critical
--
You received this bug notification
** Branch linked: lp:~rvb/maas/reporting-bug-1301809
** Changed in: maas
Milestone: None => 14.10
** Changed in: maas
Assignee: (unassigned) => Raphaël Badin (rvb)
** Changed in: maas
Status: Triaged => In Progress
** Also affects: maas/1.5
Importance: Undecided
Status
Well, it's the reporting task that broke because of the absence of
'/var/lib/maas/boot-resources/current/'. The easiest way to fix this is
to change the reporting task so that it copes with that.
** Changed in: maas
Importance: Undecided => Critical
** Changed in: maas
Status: New => T
After I asked the cluster controller to import boot images, the
directory was created and report_boot_images tasks are now reported as
successful.
Perhaps this is a packaging bug to create that directory upfront? Not
sure whose responsibility it is, but marking as affecting Ubuntu MAAS
too.
** Al
