after juju upgrade to 2.5-beta1, charm upgrade on lxd container unit results in ERROR Error: no appname for profile

[Xav Paice]

Maas 2.3.5, Juju 2.5-beta1, machines in the model are Trusty. The model was deployed with 2.4.6 and then upgraded to 2.5.

I have a model where there are a bunch of machines, some are LXDs on Trusty metal.

When I upgrade a charm (nrpe, keystone as examples, but it seems generic) the charm upgrade itself appears to work OK, but I get an error returned by the client:

ERROR Error: no appname for profile

This appears to be on principal and subordinate units, for apps running in LXD containers.

[Xav Paice (xavpaice)]

better example:

I have 3 units of openstack-dashboard, running cs:openstack-dashboard-268, and upgrade them to -271:

$ juju upgrade-charm --debug openstack-dashboard
22:13:43 INFO juju.cmd supercommand.go:56 running juju [2.5-beta1 gc go1.10.4]
22:13:43 DEBUG juju.cmd supercommand.go:57 args: []string{"/snap/juju/5875/bin/juju", "upgrade-charm", "--debug", "openstack-dashboard"}
22:13:43 INFO juju.juju api.go:67 connecting to API addresses: [10.245.88.10:17070]
22:13:43 DEBUG juju.api apiclient.go:883 successfully dialed "wss://10.245.88.10:17070/model/12ce57e9-789d-45c8-84ee-0b182d95b47b/api"
22:13:43 INFO juju.api apiclient.go:603 connection established to "wss://10.245.88.10:17070/model/12ce57e9-789d-45c8-84ee-0b182d95b47b/api"
22:13:44 INFO juju.juju api.go:67 connecting to API addresses: [10.245.88.10:17070]
22:13:44 DEBUG juju.api apiclient.go:883 successfully dialed "wss://10.245.88.10:17070/api"
22:13:44 INFO juju.api apiclient.go:603 connection established to "wss://10.245.88.10:17070/api"
22:13:44 DEBUG httpbakery client.go:243 client do GET https://api.jujucharms.com/charmstore/v5/xenial/openstack-dashboard/meta/any?include=id&include=supported-series&include=published {
22:13:44 DEBUG httpbakery client.go:245 } -> error <nil>
22:13:46 INFO cmd upgradecharm.go:356 Added charm "cs:openstack-dashboard-271" to the model.
22:13:47 INFO cmd upgradecharm.go:475 LXD Profile upgrade Not Required for "openstack-dashboard/3"
ERROR Error: no appname for profile charm upgrade
ERROR Error: no appname for profile charm upgrade
22:13:47 DEBUG juju.cmd.juju.application upgradecharm.go:414 the lxd profile upgrade watcher has been stopped
22:13:49 DEBUG juju.api monitor.go:35 RPC connection died
22:13:49 INFO cmd supercommand.go:465 command finished

[Heather Lanigan (hmlanigan)]

@xavpaice, what machine type was openstack-dashboard/3 running on? Compared to the other two units?

I can reproduce with:
1. bootstrap localhost with juju 2.4.6
2. deploy cs:openstack-dashboard-268 --to lxd <-- bionic default
3. upgrade to juju 2.5-beta1 <-- required
4. upgrade-charm openstack-dashboard

This bug is specific to upgrading the charm of a unit on an lxd container after upgrading to juju 2.5-beta1, where the unit was deploy with 2.4 (maybe 2.3)

[Xav Paice (xavpaice)]

LXD's, all 3.

[Heather Lanigan (hmlanigan)]

https://github.com/juju/juju/pull/9530