[snap] Preseeds are not 'common' that would allow the user to configure them

Bug #1696771 reported by Andres Rodriguez on 2017-06-08
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
High
Andres Rodriguez
2.4
Undecided
Andres Rodriguez

Bug Description

MAAS allows users to modify the preseeds so they can customize the installation. With the snaps, users are no longer able to do so because the preseeds are not installed in the common, user editable directory.

Related branches

Changed in maas:
milestone: none → 2.3.0
Blake Rouse (blake-rouse) wrote :

Probably not the best time to do this but moving them into the database would be much better. As at the moment with HA you would need to modify the preseed across all region controllers.

Changed in maas:
status: New → Triaged
importance: Undecided → Medium
importance: Medium → High
Changed in maas:
milestone: 2.3.0 → 2.3.0beta2
Changed in maas:
milestone: 2.3.0beta2 → 2.3.0beta3
Changed in maas:
milestone: 2.3.0beta3 → 2.3.0beta4
Changed in maas:
milestone: 2.3.0beta4 → 2.3.x
Florian Guitton (f-guitton) wrote :

Hello :) Do we know when this is progressing? The documentation does not explicitly mention this limitation, simply stating that "In particular, implementing high availability via snaps is not yet possible". This causes problems as we have now large deployments which we start requiring deployment of supplementary drivers for.
Best regards,

no longer affects: maas (Ubuntu)
Changed in maas:
assignee: nobody → Andres Rodriguez (andreserl)
milestone: 2.3.x → 2.5.0
no longer affects: maas/2.2
Changed in maas:
status: Triaged → In Progress
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
milestone: 2.5.0 → 2.5.0alpha1
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