With Azure, management-certificate-path should not be required if management-certificate is set in the juju environment
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-quickstart |
Triaged
|
High
|
Unassigned |
Bug Description
When using quickstart with a juju environment.yaml which has management-
juju --debug quickstart -e test-release-azure2 --constraints mem=2G --no-browser /tmp/landscape-
2015-01-16 20:54:52 INFO juju.cmd supercommand.go:37 running juju [1.20.14-
usage: juju-quickstart [-h] [-e ENV_NAME] [-n BUNDLE_NAME] [-i]
juju-quickstart: error: cannot use the test-release-azure2 environment:
a value is required for the management certificate path field
2015-01-16 20:54:53 ERROR juju.cmd supercommand.go:323 subprocess encountered error code 2
The Juju azure provider only requires "management-
With such a environment.yaml, I made the following brute force change and observed that quickstart deployment of a bundle was successful:
diff /usr/lib/
578,584d577
< fields.
< 'management-
< label='management certificate path',
< help='the path to the pem file associated to the certificate '
< 'uploaded in the Azure management console: '
< 'https:/
< '(Settings -> Management Certificates)'),
summary: |
- With Azure management-certificate-path should not be required if + With Azure, management-certificate-path should not be required if management-certificate is set in the juju environment |
tags: | added: azure juju-ci |
Changed in juju-quickstart: | |
status: | New → Triaged |
importance: | Undecided → High |