user editing of preseed files is difficult due to maas internal data
Bug #1734391 reported by
Scott Moser
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
The 'curtin_userdata' is was scary to look at, and hard to work
with for a user. Adding early_commands or late_commands meant that they
would have to edit an existing entry, and failure to do so would
break the install.
I've personally been annoyed by this [1], and customers have had problems
also resulting in bugs like bug 1734274.
[1] https:/
Related bugs:
* bug 1734274: curtin fails to deploy on some invalid configs.
Related branches
~smoser/maas:cleanup/render-curtin-config-internally
- MAAS Lander: Needs Fixing
- Mike Pontillo (community): Needs Information
- Andres Rodriguez: Pending requested
-
Diff: 640 lines (+224/-127)7 files modifiedcontrib/preseeds_v2/curtin_userdata (+18/-42)
contrib/preseeds_v2/curtin_userdata_centos (+3/-9)
contrib/preseeds_v2/curtin_userdata_windows (+2/-10)
src/maasserver/node_action.py (+2/-2)
src/maasserver/preseed.py (+133/-6)
src/maasserver/tests/test_node_action.py (+21/-21)
src/maasserver/tests/test_preseed.py (+45/-37)
| Changed in maas: | |
| milestone: | none → 2.4.x |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| tags: | added: cpe-onsite |
Revision history for this message
| Adam Collard (adam-collard) wrote | #1 |
| Changed in maas: | |
| status: | Triaged → Invalid |
To post a comment you must log in.
This bug has not seen any activity in the last 6 months, so it is being automatically closed.
If you are still experiencing this issue, please feel free to re-open.
MAAS Team