Comment 5 for bug 1836226

The fact that one of our flagship bundles needs --force to operate means we
need to rethink *something* in the mix. (Either we need to back off from
refusing disk because it really is needed, or we should try to rework how
enable that support.)

That said, I agree with Rick that we could defer the --force out of
'deploy' and into 'add-unit'.

On Mon, Jul 22, 2019 at 4:50 PM Richard Harding <email address hidden>
wrote:

> Though I do think that the best thing is to try to avoid things in the
> profile that need --force if at all possible. It was setup in this way
> with collaboration with the lxd team and it's a generally not great to
> have things in there that require it if it can be helped.
>
> ** Changed in: juju
> Status: New => Triaged
>
> ** Changed in: juju
> Importance: Undecided => Medium
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1836226
>
> Title:
> juju will attempt to deploy a lxd profile on a non-lxd cloud
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1836226/+subscriptions
>