Loading state on bootstrap ignores ssl-hostname-verification setting
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Martin Packman | ||
1.16 |
Fix Released
|
High
|
Martin Packman | ||
juju-core (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Saucy |
Won't Fix
|
High
|
Unassigned |
Bug Description
[Impact]
Users of private cloud deployments with self-signed SSL certs can't use Juju
[Test Case]
#Requires cloud with swift storage using self-signed cert
juju bootstrap --debug
#fail
[Regression Potential]
Minimal code change in direct path only.
[Original Bug Report]
In a private openstack cloud setup, using self-signed certs, juju fails to bootstrap even with ssl-hostname-
+ echo https:/
+ /var/lib/
2014-01-13 07:05:33 DEBUG juju.agent agent.go:237 Reading agent config, format: format 1.16
2014-01-13 07:05:33 DEBUG juju.agent agent.go:464 initializing address [localhost:37017]
2014-01-13 07:05:33 INFO juju.state open.go:68 opening state; mongo addresses: ["localhost:
2014-01-13 07:05:33 INFO juju.state open.go:106 connection established
2014-01-13 07:05:34 INFO juju.state open.go:136 initializing environment
2014-01-13 07:05:35 DEBUG juju.agent agent.go:474 state initialized
2014-01-13 07:05:35 DEBUG juju.agent agent.go:486 adding admin user
2014-01-13 07:05:37 DEBUG juju.agent agent.go:497 setting password hash for admin user
2014-01-13 07:05:39 ERROR juju supercommand.go:282 cannot load state from URL "https:/
failed: /var/lib/
Related branches
- Juju Engineering: Pending requested
-
Diff: 183 lines (+63/-16)5 files modifiedcmd/jujud/bootstrap.go (+1/-1)
environs/httpstorage/storage.go (+4/-1)
provider/common/bootstrap_test.go (+1/-1)
provider/common/state.go (+11/-2)
provider/common/state_test.go (+46/-11)
Changed in juju-core: | |
importance: | Undecided → High |
status: | New → In Progress |
milestone: | none → 1.17.1 |
Changed in juju-core: | |
assignee: | nobody → Martin Packman (gz) |
Changed in juju-core: | |
milestone: | 1.17.1 → 1.18.0 |
Changed in juju-core (Ubuntu): | |
status: | New → Fix Released |
Changed in juju-core (Ubuntu Saucy): | |
importance: | Undecided → High |
status: | New → Triaged |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
description: | updated |
Hi Martin. Should the status of this bug be fix committed in trunk? Do we need to merge the branch in trunk?