yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxxxxxxxxxx>]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY


** Changed in: nova
       Status: Confirmed => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1273894

Title:
  GlusterFS: Do not time out long-running volume snapshot operations

Status in Cinder:
  New
Status in OpenStack Compute (nova):
  Expired

Bug description:
  Currently, when Cinder sends a snapshot create or delete job to Nova
  for the GlusterFS driver, it has a fixed timeout window, and if the
  job takes longer than that, the snapshot operation is failed.  (The
  assumption is that Nova has somehow failed.)

  This is problematic because it fails operations that are still active
  but running very slowly.

  The fix proposed here is to use the same update_snapshot_status API
  which is used to finalize these operations to send periodic updates
  while the operation is in progress, so that Cinder knows that Nova is
  still active, and that the job does not need to be timed out.

  This is backward compatible for both Havana Cinder and Havana Nova.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1273894/+subscriptions