non-interactive add-cloud discards existing description

Bug #1646203 reported by Aaron Bentley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Expired
Medium
Unassigned

Bug Description

non-interactive add-cloud drops the existing description field.
(This is different from bug #1645783, where *interactive* add-cloud doesn't *prompt* for a description field.)

This is similar to a known bug that update-clouds discards this description field, and probably has the same root cause.

Since add-cloud is used with private clouds, for which a generic built-in description is typically unsuitable (and vsphere and manual don't even have generic built-in descriptions), discarding this field is much worse than the update-clouds case.

Tested with revision-build 4160/7b7d4a4
$ `jver 2.1-4610` add-cloud vsphere ~/canonical/cloud-city/example-clouds.yaml
$ cat $JUJU_DATA/clouds.yaml
clouds:
  vsphere:
    type: vsphere
    auth-types: [userpass]
    endpoint: 10.245.0.131
    regions:
      dc0:
        endpoint: 10.245.0.131
$ cat ~/canonical/cloud-city/example-clouds.yaml
clouds:
  vsphere:
    type: vsphere
    auth-types: [userpass]
    endpoint: 10.245.0.131
    regions:
      dc0:
        endpoint: 10.245.0.131
    description: 'foo'
$ `jver 2.1-4610` --version
2.1-beta2-xenial-amd64

Changed in juju:
milestone: 2.1.0 → 2.2.0
assignee: nobody → Richard Harding (rharding)
Revision history for this message
Anastasia (anastasia-macmood) wrote :

Marked as Won't Fix for 2.0.x as no further 2.0.x releases are planned.

Changed in juju:
assignee: Richard Harding (rharding) → nobody
Curtis Hovey (sinzui)
Changed in juju:
milestone: 2.2-beta1 → 2.2-beta2
Curtis Hovey (sinzui)
Changed in juju:
milestone: 2.2-beta2 → 2.2-beta3
Changed in juju:
milestone: 2.2-beta3 → 2.2-beta4
Changed in juju:
milestone: 2.2-beta4 → 2.2-rc1
Tim Penhey (thumper)
Changed in juju:
importance: High → Medium
milestone: 2.2-rc1 → none
no longer affects: juju/2.0
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.

Changed in juju:
status: Triaged → Expired
tags: added: expirebugs-bot
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.