Unable to find implementation for relation: provides of nova-designate

Bug #1756852 reported by Dmitrii Shcherbakov on 2018-03-19
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Designate Charm
Low
Unassigned

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/0.juju-log Unable to find implementation for relation: provides of nova-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://github.com/juju/layer-index/tree/master/interfaces

Dmitrii Shcherbakov (dmitriis) wrote :
Download full text (5.6 KiB)

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
unit-designate-2: 14:58:18 ERROR unit.designate/2.juju-log shared-db:73: Unable to find implementation for relation: provides of nova-designate
unit-designate-bind-0: 14:58:18 DEBUG unit.designate-bind/0.dns-backend-relation-joined active
unit-designate-bind-0: 14:58:18 INFO juju.worker.uniter.operation ran "dns-backend-relation-joined" hook
unit-designate-bind-0: 14:58:18 INFO unit.designate-bind/0.juju-log dns-backend:69: Reactive main running for hook dns-backend-relation-changed
unit-designate-2: 14:58:18 INFO unit.designate/2.juju-log shared-db:73: Invoking reactive handler: hooks/relations/mysql-shared/requires.py:15:joined
unit-designate-2: 14:58:18 INFO unit.designate/2.juju-log shared-db:73: Invoking reactive handler: reactive/designate_handlers.py:60:clear_dns_config_available
unit-designate-2: 14:58:18 INFO unit.designate/2.juju-log shared-db:73: Invoking reactive handler: reactive/designate_handlers.py:224:run_assess_status_on_every_hook
unit-designate-2: 14:58:18 INFO unit.designate/2.juju-log shared-db:73: Invoking reactive handler: reactive/designate_handlers.py:88:setup_database

Likewise, on -next:

 juju upgrade-charm designate --switch cs:~openstack-charmers-next/designate --force-units
Added charm "cs:~openstack-charmers-next/designate-84" to the model.

https://paste.ubuntu.com/p/qnFR48cpw7/

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
2 started 10.232.24.3 node-0e6956f8-5daf-11e4-b187-525400a6ab07 xenial default Deployed
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'
unit-designate-2: 14:55:02 ERROR unit.designate/2.juju-log Unable to find implementation for relation: provides of nova-designate
unit-designate-2: 14:58:06 ERROR unit.designate/2.juju-log Unable to find implementation for relation: provides of nova-designate
unit-designate-2: 14:58:08 ERROR unit.designate/2.juju-log Unable to find implementation for relation: provides of nova-designate
unit-designate-2: 14:58:11 ERROR unit.designate/2.juju-log Unable to find implementation for relation: provides of nova-designate
unit-designate-2: 14:58:18 ERROR unit.designate/2.juju-log shared-db:73: Unable to find implementation for relation: provides of nova-designat...

Read more...

James Page (james-page) wrote :

Errors out is not quite true - reactive logs an ERROR message because it can't find the implmenetation.

Changed in charm-designate:
status: New → Triaged
importance: Undecided → Low
James Page (james-page) wrote :

Lets just drop the provides entry from the designate charm.

Christian Reis (kiko) wrote :

Not sure about "errors out", but we saw this kill this run: https://solutions.qa.canonical.com/#/qa/testRun/04bd84a2-da33-4244-9afc-a3513e26d442

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers