Stuck on 'shared-db' incomplete, Waiting for proxied DB creation from cluster

Bug #1887265 reported by Luis Felipe Domínguez Vega
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL Router Charm
Invalid
Undecided
Unassigned
OpenStack Designate Charm
Fix Released
Undecided
Unassigned

Bug Description

I'm changing from percona cluster to Innodb cluster. So I was started with designate service, backup designate DB from percona and restore on innodb cluster. Then i deployed the mysql-router (as designate-mysql-router). Added relation from designate with designate-mysql-router.

Now the problem is that when I add the relation from designate-mysql-router to innodb-cluster the charm is stuck on state "'shared-db' incomplete, Waiting for proxied DB creation from cluster" and wait, wait but nothing happen

Revision history for this message
Luis Felipe Domínguez Vega (luis.dominguez) wrote :

this happen only on my designate charm... i tried with keystone charm and is worked great.

Revision history for this message
Luis Felipe Domínguez Vega (luis.dominguez) wrote :

sems a designate charm problem... because only designate is getting that error... and when i relate with the old percona cluster.. i need remove a unit and recreate.. then the db relation work

Changed in charm-mysql-router:
status: New → Invalid
Revision history for this message
Zhanglei Mao (zhanglei-mao) wrote :

I got this issue too after I remove relation (mysql-innodb-cluster:db-router keystone-mysql-router:db-routerand) and add it back again. I did this relation change as one of keystone unit is in the blocked state of "Allowed_units list provided but this unit not present'

Revision history for this message
Diko Parvanov (dparv) wrote (last edit ):

+1 on designate charm, same reported behavior; adding charm-designate

after adding the relation:
designate/0 waiting idle 6/lxd/2 10.254.1.220 9001/tcp 'shared-db' incomplete
  designate-mysql-router/9* waiting idle 10.254.1.220 'shared-db' incomplete, Waiting for proxied DB creation from cluster

Revision history for this message
Diko Parvanov (dparv) wrote :

This was fixed in our case by:

re-adding the relations to mysql-innodb-cluster and running clearing the shared-db.setup flag and update-status next:

juju run -u designate/X charms.reactive clear_flag shared-db.setup
juju run -u designate/X hooks/update-status

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-designate (master)
Changed in charm-designate:
status: New → In Progress
Changed in charm-designate:
milestone: none → 21.10
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-designate (master)

Reviewed: https://review.opendev.org/c/openstack/charm-designate/+/801369
Committed: https://opendev.org/openstack/charm-designate/commit/4e9d4756a2003859d668e7233fc3e38e0c72c390
Submitter: "Zuul (22348)"
Branch: master

commit 4e9d4756a2003859d668e7233fc3e38e0c72c390
Author: David Ames <email address hidden>
Date: Mon Jul 19 10:32:39 2021 -0700

    Clear shared-db.setup when departing shared-db

    When shared-db is rejoined the charm will reconfigure the DB IFF DB
    related flags are cleared.

    Change-Id: Ieb575d6aa220f10c519425f1e1a6f59e29c512f1
    Closes-Bug: #1887265

Changed in charm-designate:
status: In Progress → Fix Committed
Changed in charm-designate:
status: Fix Committed → Fix Released
Revision history for this message
Vahid Alimohamadi (cybercoder) wrote :

After remove a keystome unit and add new one:

Unit Workload Agent Machine Public address Ports Message
keystone/0 active idle 3/lxd/2 192.168.50.73 5000/tcp Unit is ready
  keystone-hacluster/1 active idle 192.168.50.73 Unit is ready and clustered
  keystone-mysql-router/28 waiting idle 192.168.50.73 'db-router' incomplete, Waiting for proxied DB creation from cluster
keystone/2 active idle 5/lxd/3 192.168.50.77 5000/tcp Unit is ready
  keystone-hacluster/2 active idle 192.168.50.77 Unit is ready and clustered
  keystone-mysql-router/27* waiting idle 192.168.50.77 'db-router' incomplete, Waiting for proxied DB creation from cluster
keystone/3* active idle 4/lxd/18 192.168.50.143 5000/tcp Unit is ready
  keystone-hacluster/3* active idle 192.168.50.143 Unit is ready and clustered
  keystone-mysql-router/29 waiting idle 192.168.50.143 'db-router' incomplete, Waiting for proxied DB creation from cluster

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.