provide --storage flag on add-unit

[Stuart Bishop]

I can add a new unit and reuse existing storage with 'juju add-unit --attach-storage foo/1'. However, there seems to be no way to add a new unit with fresh, attached storage. There is no 'juju add-unit --storage=1G' or similar, or easy way to create a clean, unattached storage.

Use case is adding a second unit to a production-sized PostgreSQL deployment:

juju deploy cs:postgresql --storage=250G

If I need to add a second unit with 'juju add-unit postgresql', there will be no attached storage and setup will fail; an attempt will be made to replicate the database, and it will fail due to lack of space.

[Andrew Wilkins (axwalk)]

> juju deploy cs:postgresql --storage=250G
>
> If I need to add a second unit with 'juju add-unit postgresql', there will be no attached storage > and setup will fail; an attempt will be made to replicate the database, and it will fail due to lack of space.

If you deploy with --storage, then every unit added with add-unit will get the same storage. I've just tested this with 2.3 and verified that it works.

It might still be useful to have a --storage flag on add-unit, though, to override whatever was specified to "juju deploy".

[Stuart Bishop (stub)]

Thanks, I can confirm it works as you describe too. However, if storage was added to the first unit *after* the initial deploy (using add-storage), the second unit does not implicitly get storage and will fail as I describe. So yes, a --storage flag on add-unit would be useful.

[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.