init system discovery script fails with: [[: not found
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Eric Snow | ||
1.23 |
Fix Released
|
High
|
Eric Snow | ||
1.24 |
Fix Released
|
High
|
Eric Snow |
Bug Description
On 1.24 after https:/
1. the runcmd script cloud-init generates from the given user-data starts with a "#!/bin/sh" shebang.
2. the init_system=$(...) line contains a bash-specific script, which is just inlined (see an excerpt of the user-data - http://
If I apply the following patch it works without errors: http://
We need to be careful when using "bashisms" in scripts and only do so when we're generating a script file to run, not when inlining scripts run (most likely) by /bin/sh in cloud-init runcmds.
UPDATE: #2359 was reverted from 1.24, but the problem is still there I believe, and master should be affected as well.
Changed in juju-core: | |
status: | Triaged → In Progress |
assignee: | nobody → Eric Snow (ericsnowcurrently) |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
tags: | added: tech-debt |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
For 1.23: http:// reviews. vapour. ws/r/1737/ reviews. vapour. ws/r/1738/
For 1.23/master: http://