MAAS 1.7 should be backwards compatible with 1.5 the preseed naming convention

Bug #1439366 reported by Andres Rodriguez on 2015-04-01
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Critical
Raphaël Badin
1.8
Critical
Raphaël Badin

Bug Description

MAAS 1.5 supported preseeds in the way of:

{prefix}_{node_arch}_<etc>

MAAS 1.7 supports them in the way of:

{prefix}_{osystem}_{node_arch}_<etc>

In 1.7, we added the ability to specify an OS system. However, older preseeds files won't be recognized by maas given that the osytem is not in the path of the preseed. MAAS 1.7 needs to assume that if no osystem is provided, it should asume 'ubuntu' by default for backwards compatible.

Related branches

Changed in maas:
milestone: none → 1.7.3
importance: Undecided → Critical
status: New → Triaged
Raphaël Badin (rvb) on 2015-04-03
Changed in maas:
assignee: nobody → Raphaël Badin (rvb)
Raphaël Badin (rvb) on 2015-04-03
Changed in maas:
status: Triaged → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
Andres Rodriguez (andreserl) wrote :

This bug has been reported and fixed on upstream MAAS. However, provided that the bug was listed on the debian changelog, this appears as needing verification for pending SRU [1]. This bug did not affect current MAAS in Ubuntu, hence setting this to verification-done to unblock pending SRU.

[1]:http://people.canonical.com/~ubuntu-archive/pending-sru.html

tags: added: verification-done
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers