Add subnet documentation confusingly compares `add-subnet` to itself
Bug #1807956 reported by
Eric Claude Jones
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
The `juju add-subnet` command help documentation reads:
Adds an existing subnet to Juju, making it available for use. Unlike
"juju add-subnet", this command does not create a new subnet, so it
is supported on a wider variety of clouds (where SDN features are not
available, e.g. MAAS). The subnet will be associated with the given
existing Juju network space."
Notice how the documentation states, 'Unlike "juju add-subnet", this command...'. This is confusing since a reader cannot easily infer what the correct sentence/command might actually be.
| description: | updated |
| description: | updated |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Low → Medium |
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.