Chris Friesen <chris.frie...@windriver.com> wrote on 11/05/2013 10:21:07 PM: > > I think the proper fix is to make sure that Cinder is moving the volume > > into 'error' state in all cases where there is an error. Nova can then > > poll as long as its in the 'downloading' state, until it's 'available' or > > 'error'. Is there a reason why Cinder would legitimately get stuck in > > 'downloading'? > > There's always the "cinder service crashed and couldn't restart" case. :)
Well we should fix that too :) Your Cinder processes should be properly HA'ed, and yes, Cinder needs to be robust enough to resume operations. I don't see how adding a callback would help - wouldn't you still need to timeout if you don't get a callback? Thanks, Avishay _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
