Doing some research. 1) I don't think this is more than one charm unit trying to do migrations at the same time (comment #2) 2) The problem is barbican itself failing per the Traceback 3) My current theory is a failed migration attempt that leaves behind two alembic versions.
Per [1] we should only ever expect 1 alembic version at a time. As a work around we may need to do some DB surgery per [1]. After a backup of course. To find what gets barbican into this state will take a bit more digging through logs. [1] https://stackoverflow.com/questions/42424320/how-do-i-fix-alembics- requested-revision-overlaps-with-other-requested-revisio -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827690 Title: [19.04][stein] barbican-worker is down: Requested revision 1a0c2cdafb38 overlaps with other requested revisions 39cf2e645cba To manage notifications about this bug go to: https://bugs.launchpad.net/charm-barbican/+bug/1827690/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
