juju deploy --storage does not accept syntax accepted by juju add-storage

[Tim McNamara]

The 'juju deploy --storage=<options>' does not allow storage to be specified that defers to the model's defaults (example 1). This means that syntax accepted by 'juju add-storage <unit> <options>' (example 4) do not match exactly.

On an AWS-hosted model..

  $ juju deploy pg1 --storage pgdata
  ERROR invalid value "pgdata" for option --storage: expected [<application>:]<store>=<constraints>

  $ juju deploy pg1 --storage pgdata=ebs
  Located charm "cs:postgresql-207".
  Deploying charm "cs:postgresql-207".

  $ juju deploy postgresql pg2
  Located charm "cs:postgresql-207".
  Deploying charm "cs:postgresql-207".

  $ juju add-storage pg2/0 pgdata
  added storage pgdata/1 to pg2/0

[Ian Booth (wallyworld)]

At deploy time, you must provide enough info to allow juju to set up storage.
Once juju is deployed, adding storage will just use the same parameters as at deploy (unless otherwise specified) so that's why there's less parameters.

[Tim McNamara (tim-clicks)]

Makes sense, we will treat this as a doc fix then.

The help text for `juju help add-storage` includes this sentence: "Specify
a unit and a storage specification in the same format
as passed to juju deploy --storage=”...”."

On Thu, 18 Jun 2020, 22:20 Ian Booth <<email address hidden> wrote:

> At deploy time, you must provide enough info to allow juju to set up
> storage.
> Once juju is deployed, adding storage will just use the same parameters as
> at deploy (unless otherwise specified) so that's why there's less
> parameters.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1884013
>
> Title:
> juju deploy --storage does not accept syntax accepted by juju add-
> storage
>
> Status in juju:
> Triaged
>
> Bug description:
> The 'juju deploy --storage=<options>' does not allow storage to be
> specified that defers to the model's defaults (example 1). This means
> that syntax accepted by 'juju add-storage <unit> <options>' (example
> 4) do not match exactly.
>
> On an AWS-hosted model..
>
> $ juju deploy pg1 --storage pgdata
> ERROR invalid value "pgdata" for option --storage: expected
> [<application>:]<store>=<constraints>
>
> $ juju deploy pg1 --storage pgdata=ebs
> Located charm "cs:postgresql-207".
> Deploying charm "cs:postgresql-207".
>
> $ juju deploy postgresql pg2
> Located charm "cs:postgresql-207".
> Deploying charm "cs:postgresql-207".
>
> $ juju add-storage pg2/0 pgdata
> added storage pgdata/1 to pg2/0
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1884013/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: product=juju; status=Triaged; importance=Medium;
> assignee=None;
> Launchpad-Bug-Tags: bitesize deploy storage
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: tim-clicks wallyworld
> Launchpad-Bug-Reporter: Tim McNamara (tim-clicks)
> Launchpad-Bug-Modifier: Ian Booth (wallyworld)
> Launchpad-Message-Rationale: Subscriber
> Launchpad-Message-For: tim-clicks
>

[Canonical Juju QA Bot (juju-qa-bot)]

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.