mysql-routers in error state when deploying barbican

Bug #2044128 reported by Marian Gasparovic
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Snap
Triaged
Medium
Unassigned

Bug Description

After `sunbeam enable caas` barbican-mysql-router units went to error state

barbican-mysql-router/0 error idle 10.1.155.114 hook failed: "update-status"
barbican-mysql-router/1 error idle 10.1.29.189 hook failed: "backend-database-relation-changed"
barbican-mysql-router/2* active executing 10.1.37.49
barbican-mysql/0 maintenance idle 10.1.37.51 joining the cluster
barbican-mysql/1* maintenance idle 10.1.155.116 Unable to get member state
barbican-mysql/2 waiting idle 10.1.29.191 waiting to get cluster primary from peers

Logs and artifacts - https://oil-jenkins.canonical.com/artifacts/cc4e0b9f-117a-411f-b84a-454661b76af0/index.html

Tags: cdo-qa
James Page (james-page)
Changed in snap-openstack:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
James Page (james-page) wrote :
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.