Unable to find implementation for relation: provides of nova-designate
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Designate Charm |
Fix Released
|
Low
|
Edward Hope-Morley |
Bug Description
While nova-designate integration is not something that we'd use in the future due to neutron <-> designate integration, designate charm currently has nova-designate juju interface and it errors out as there is no such interface included in layer.yaml.
In fact, it was never there because only nova, being a classic charm, uses that relation to do something meaningful.
unit-designate-0: 11:13:04 ERROR unit.designate/
provides:
dnsaas:
interface: designate
nova-designate:
interface: nova-designate
No such interface here (and so such interface in layer.yaml file for designate):
https:/
Changed in charm-designate: | |
status: | Fix Committed → Fix Released |
On 18.02:
unit-designate-2: 14:58:18 INFO unit.designate/ 2.juju- log shared-db:73: Reactive main running for hook shared- db-relation- joined 2.juju- log shared-db:73: Unable to find implementation for relation: provides of nova-designate bind-0: 14:58:18 DEBUG unit.designate- bind/0. dns-backend- relation- joined active bind-0: 14:58:18 INFO juju.worker. uniter. operation ran "dns-backend- relation- joined" hook bind-0: 14:58:18 INFO unit.designate- bind/0. juju-log dns-backend:69: Reactive main running for hook dns-backend- relation- changed 2.juju- log shared-db:73: Invoking reactive handler: hooks/relations /mysql- shared/ requires. py:15:joined 2.juju- log shared-db:73: Invoking reactive handler: reactive/ designate_ handlers. py:60:clear_ dns_config_ available 2.juju- log shared-db:73: Invoking reactive handler: reactive/ designate_ handlers. py:224: run_assess_ status_ on_every_ hook 2.juju- log shared-db:73: Invoking reactive handler: reactive/ designate_ handlers. py:88:setup_ database
unit-designate-2: 14:58:18 ERROR unit.designate/
unit-designate-
unit-designate-
unit-designate-
unit-designate-2: 14:58:18 INFO unit.designate/
unit-designate-2: 14:58:18 INFO unit.designate/
unit-designate-2: 14:58:18 INFO unit.designate/
unit-designate-2: 14:58:18 INFO unit.designate/
Likewise, on -next:
juju upgrade-charm designate --switch cs:~openstack- charmers- next/designate --force-units charmers- next/designate- 84" to the model.
Added charm "cs:~openstack-
https:/ /paste. ubuntu. com/p/qnFR48cpw 7/
juju status designate
Model Controller Cloud/Region Version SLA
default samaas samaas 2.4-beta3 unsupported
App Version Status Scale Charm Store Rev OS Notes
designate 2.1.0 active 1 designate jujucharms 84 ubuntu
Unit Workload Agent Machine Public address Ports Message
designate/2* active idle 2/lxd/7 10.232.45.150 9001/tcp Unit is ready
Machine State DNS Inst id Series AZ Message 5daf-11e4- b187-525400a6ab 07 xenial default Deployed
2 started 10.232.24.3 node-0e6956f8-
2/lxd/7 started 10.232.45.150 juju-a06185-2-lxd-7 xenial default Container started
There are a bunch of those errors but eventually designate units get to active/idle:
designate/2* active idle 2/lxd/7 10.232.45.150 9001/tcp Unit is ready
juju debug-log -i designate/2 --replay | grep 'Unable to find implementation for relation: provides of nova-designate' 2.juju- log Unable to find implementation for relation: provides of nova-designate 2.juju- log Unable to find implementation for relation: provides of nova-designate 2.juju- log Unable to find implementation for relation: provides of nova-designate 2.juju- log Unable to find implementation for relation: provides of nova-designate 2.juju- log shared-db:73: Unable to find implementation for relation: provides of nova-designat...
unit-designate-2: 14:55:02 ERROR unit.designate/
unit-designate-2: 14:58:06 ERROR unit.designate/
unit-designate-2: 14:58:08 ERROR unit.designate/
unit-designate-2: 14:58:11 ERROR unit.designate/
unit-designate-2: 14:58:18 ERROR unit.designate/