Comment 1 for bug 1836226

I don't see why an invalidity crafted charm should be ignored. It is always
possible on any cloud that you would "add-unit --to lxd:3" which would put
the unit into a container where the profile would be in play. While we
could wait until you try to create a container, it does feel like a case
where we shouldn't be accepting bad data in the first place.

John
=:->

On Thu, Jul 11, 2019, 20:40 Peter De Sousa <email address hidden>
wrote:

> Public bug reported:
>
> Hello,
>
>
> When embedding a profile with unsupported keys Juju will attempt to deploy
> this profile even if the cloud is not a lxd cloud.
>
> Steps to reproduce:
>
> 1. Create a non-lxd cloud
> 2. use a charm with a unsupported lxd profile like this one:
> https://pastebin.canonical.com/p/Bh5KGRrQtK/
> 3. Attempt to deploy the charm either in a bundle or on it's own without
> --force
> 4. Observe that juju will fail with 'ERROR invalid lxd-profile.yaml:
> contains device type "disk"' or other unsupported key value.
>
> Expected Behaviour:
>
> Juju ignores profile and deploys
>
> Actual:
>
> Deployment fails with error in step 4.
>
> Cheers,
> Peter
>
> ** Affects: juju
> Importance: Undecided
> Status: New
>
> --
> 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
>