Empty constraint value lost during some cloud-init step
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Invalid
|
High
|
Tim Penhey | ||
1.16 |
Invalid
|
High
|
Tim Penhey | ||
juju-core (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Saucy |
Invalid
|
Undecided
|
Unassigned | ||
Trusty |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[Impact]
??
[Test Case]
??
[Regression Potential]
Minimal
[Original Bug Report]
There was a problem with the cloud-init userdata part of the boot, where it appears that the running of the scripts removed the quotes. Inside the yaml file, the scripts is an array of strings, and the params look like:
--constraints ''
Also noteworthy is that the --env-config is similarly quoted, and the command line in the pastebin didn't have the single quotes around that either.
Low importance as we are working around the bug by no longer passing through empty constraints on the command line.
This is from the pastebin:
ubuntu@ta3r4:~$ /var/lib/
error: invalid value "--debug" for flag --constraints: malformed constraint "--debug"
Related branches
- Tim Penhey (community): Approve
-
Diff: 15 lines (+5/-0)1 file modifiedprovider/local/environ.go (+5/-0)
Changed in juju-core: | |
milestone: | none → 1.16.1 |
importance: | Low → High |
assignee: | nobody → Tim Penhey (thumper) |
status: | Invalid → Fix Committed |
milestone: | 1.16.1 → 1.17.0 |
description: | updated |
Changed in juju-core (Ubuntu Trusty): | |
status: | Fix Released → Invalid |
Changed in juju-core (Ubuntu Saucy): | |
status: | New → Invalid |
Changed in juju-core: | |
status: | Fix Committed → Invalid |
Not a bug, the echoing of the command into the logs does not quote the parameters, so the empty param was now shown. When this line was then copied and executed the empty parameter was missed.