compose_curtin_network_preseed breaks installation of all other operating systems
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Jeroen T. Vermeulen |
Bug Description
Interface configuration is OS specific, this needs to be limited to Ubuntu for the moment. Currently this is ran no matter the OS, which breaks all other os installation.
This is deploying CentOS:
chroot: failed to run command '/usr/local/
Unexpected error while running command.
Command: ['curtin', 'in-target', '--', '/usr/local/
Exit code: 127
Reason: -
Stdout: ''
Stderr: ''
2014-09-23 20:02:29,971 - util.py[WARNING]: Failed running /var/lib/
2014-09-23 20:02:29,972 - cc_scripts_
2014-09-23 20:02:29,973 - util.py[WARNING]: Running scripts-user (<module 'cloudinit.
Related branches
- Blake Rouse (community): Needs Fixing
- Raphaël Badin (community): Approve
-
Diff: 142 lines (+31/-12)3 files modifiedsrc/maasserver/preseed.py (+9/-0)
src/maasserver/tests/test_preseed.py (+19/-11)
src/maasserver/views/nodes.py (+3/-1)
Changed in maas: | |
status: | Triaged → In Progress |
milestone: | none → 1.7.0 |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Thanks for reporting this — it comes as a bit of a shock because interface configuration was already limited to Ubuntu. The config to install that script is included on all operating systems and the command to run it is included on all operating systems, but the script does nothing if the operating system install it sees is not Ubuntu.
So apparently the combination of installing a file through Curtin and then executing it through Curtin is Ubuntu-specific in some way. It's understandable that Windows gives us some trouble, because it won't have /usr/local/bin. But CentOS..?