loopingcall change regresses Trove

Bug #1738281 reported by Manoj Kumar
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

From what I can tell this commit seems to be causing a regression in Trove:


The affected Trove code is here:


The symptoms are that loopingcall ERRORs out.

From looking at the logs, is the backoff not working:


The 1.28.1 tag for oslo is broken for Trove as a result. We will have to blacklist this version until a fix is available.

Revision history for this message
Rico Lin (rico-lin) wrote :

A revert for the previous commit: https://review.openstack.org/#/c/528202

Revision history for this message
ChangBo Guo(gcb) (glongwave) wrote :

Just quick approve the revert commit

Changed in oslo.service:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers