Upgrade of principal charm with relation to subordinate with LXD profile fails with ERROR Error: Requested profile doesn't exist
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Heather Lanigan |
Bug Description
It appears that the above message always is presented to the user when upgrading a principal charm related to a subordinate charm which has a LXD profile.
As a result the machine holding the principal charm is put into a error state.
Environment:
$ juju --version
2.5-beta2-
$ snap info juju | grep installed:
installed: 2.5-beta2+
Steps to reproduce:
$ juju bootstrap --no-gui localhost
$ charm pull ubuntu
$ juju deploy ./ubuntu
$ juju deploy neutron-openvswitch
$ juju add-relation ubuntu:juju-info neutron-
< wait for deployment to complete, neutron-openvswitch will be blocked on missing relations but that is not important for the test >
$ juju upgrade-charm ubuntu --path ./ubuntu
Added charm "local:
ERROR Error: Requested profile 'juju-default-
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
default localhost-localhost localhost/localhost 2.5-beta2 unsupported 06:04:02+01:00
App Version Status Scale Charm Store Rev OS Notes
neutron-openvswitch 12.0.5 blocked 1 neutron-openvswitch jujucharms 255 ubuntu
ubuntu 18.04 active 1 ubuntu local 1 ubuntu
Unit Workload Agent Machine Public address Ports Message
ubuntu/0* active idle 0 10.130.236.177 ready
neutron-
Machine State DNS Inst id Series AZ Message
0 error 10.130.236.177 juju-7284c9-0 bionic cannot upgrade machine's lxd profile: Requested profile 'juju-default-
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Heather Lanigan (hmlanigan) |
milestone: | none → 2.5-beta2 |
Changed in juju: | |
milestone: | 2.5-beta2 → 2.5-beta3 |
Changed in juju: | |
milestone: | 2.5-beta3 → 2.5-rc1 |
Changed in juju: | |
status: | Triaged → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Same issue with MaaS provider:
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
default maas maas 2.5-beta2 unsupported 06:47:01+01:00
App Version Status Scale Charm Store Rev OS Notes
neutron-openvswitch 12.0.5 blocked 1 neutron-openvswitch jujucharms 255 ubuntu
ubuntu 18.04 active 1 ubuntu local 0 ubuntu
Unit Workload Agent Machine Public address Ports Message openvswitch/ 0* blocked idle 172.16.122.252 Missing relations: messaging
ubuntu/0* active idle 0/lxd/0 172.16.122.252 ready
neutron-
Machine State DNS Inst id Series AZ Message
0 started 172.16.122.251 rkxagy bionic default Deployed
0/lxd/0 started 172.16.122.252 juju-418942-0-lxd-0 bionic default Container started
$ juju upgrade-charm ubuntu --path ./ubuntu bionic/ ubuntu- 1" to the model. ubuntu- 1
Added charm "local:
ERROR Error: Profile doesn't exist: juju-default-
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
default maas maas 2.5-beta2 unsupported 06:48:34+01:00
App Version Status Scale Charm Store Rev OS Notes
neutron-openvswitch 12.0.5 blocked 1 neutron-openvswitch jujucharms 255 ubuntu
ubuntu 18.04 active 1 ubuntu local 1 ubuntu
Unit Workload Agent Machine Public address Ports Message openvswitch/ 0* blocked idle 172.16.122.252 Missing relations: messaging
ubuntu/0* active idle 0/lxd/0 172.16.122.252 ready
neutron-
Machine State DNS Inst id Series AZ Message ubuntu- 1
0 started 172.16.122.251 rkxagy bionic default Deployed
0/lxd/0 error 172.16.122.252 juju-418942-0-lxd-0 bionic default cannot upgrade machine's lxd profile: Profile doesn't exist: juju-default-