no armhf commissioning template

Bug #1307780 reported by Michael Hudson-Doyle on 2014-04-15
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Critical
Raphaël Badin
1.5
Critical
Raphaël Badin
maas (Ubuntu)
Critical
Unassigned

Bug Description

There is no armhf commissioning template, so when a armhf node pxe boots against maas for the first time, it gets sent an amd64/i386-ish config file, which doesn't work.

Related branches

Raphaël Badin (rvb) on 2014-04-15
Changed in maas:
importance: Undecided → Critical
Raphaël Badin (rvb) on 2014-04-15
Changed in maas:
status: New → Triaged
status: Triaged → Fix Committed
assignee: nobody → Raphaël Badin (rvb)
Changed in maas (Ubuntu):
importance: Undecided → Critical
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package maas - 1.5+bzr2252-0ubuntu1

---------------
maas (1.5+bzr2252-0ubuntu1) trusty; urgency=medium

  * New upstream release
    - Add support to install Third Party Drivers. In order for this to be
      used the user will have to go to the Settings page to enable the
      installation of these drivers. (LP: #1305839)
    - Use release images instead of daily. (LP: #1306701)
    - Quote interface name in dhcpd.template, otherwise DHCP server fails
      to start. (LP: #1306335)
    - Fix IntegrityError, when multiple processes are trying to register
      the same component. (LP: #1307415)
    - Add missing armhf commissioning template (LP: #1307780)
  * debian/maas-region-controller-min.install: Install drivers.yaml.
  * debian/maas-region-controller.postinst: No longer show the
    installation note by default. (LP: #1284652)
 -- Andres Rodriguez <email address hidden> Wed, 09 Apr 2014 19:02:00 -0400

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

Other bug subscribers