Comment 2 for bug 1226250

We think that the two belong to the same category. They are different in
details: cases described in Bug 1226233 require cross-checking states in
database and the image store (in our case, the local filesystem of the
glance host), while cases described in this post do not require such
efforts: the transition from "saving" to "killed" (or some other proper
state) can be triggered at the same time when an error is returned to the
(external) user; and the synchronization between "status=deleted" and
"deleted=True" involves checking in one DB table. Bug 1226233 may lead to
resource leakage and is harder (from our perspective) to be detected/fixed
by an external user/admin.

On Tue, Sep 17, 2013 at 12:50 AM, Fei Long Wang <email address hidden> wrote:

> Is this a dup of https://bugs.launchpad.net/glance/+bug/1226233 ?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1226250
>
> Title:
> periodic checking is needed to stabilize DB state
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/glance/+bug/1226250/+subscriptions
>