error messaging unclear when subnet is not found on bootstrap
Bug #1891692 reported by
james beedy
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Juju error messaging is unclear when a user bootstraps a controller using a subnet placement directive and the subnet is not found.
juju bootstrap aws --credential mycred --to subnet=
Creating Juju controller "aws-us-east-1" on aws/us-east-1
Looking for packaged Juju agent version 2.8.1 for amd64
Launching controller instance(s) on aws/us-east-1...
ERROR failed to bootstrap model: cannot start bootstrap instance: unknown placement directive: subnet=
The problem with the above command is that the targeted subnet doesn't exist in us-east-1, not that the placement directive is unknown.
| summary: |
- error messaging unclear when subnet is not found + error messaging unclear when subnet is not found on bootstrap |
| tags: | added: bitesize |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| milestone: | none → 2.8.3 |
| Changed in juju: | |
| milestone: | 2.8.4 → 2.9-beta1 |
| Changed in juju: | |
| milestone: | 2.9-beta1 → 2.9-rc1 |
| Changed in juju: | |
| milestone: | 2.9-rc1 → none |
| importance: | High → Medium |
| tags: | added: community-feedback |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #1 |
| Changed in juju: | |
| importance: | Medium → Low |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.