Bug #1295

If an Image in LOCKED state is deleted, the driver can leave unwanted files in the datastore

Added by Carlos Martín over 7 years ago. Updated over 7 years ago.

Status:ClosedStart date:05/25/2012
Priority:NormalDue date:
Assignee:Ruben S. Montero% Done:

0%

Category:Core & System
Target version:Release 3.6
Resolution:fixed Pull request:
Affected Versions:OpenNebula 3.4

Description

An Image in the LOCKED state is waiting for a CP SUCCESS message from the driver. If the CP operation finishes after the Image is deleted, the file will be left in the datastore.
Maybe the core could check that the Image ID returned by the CP SUCCESS does not exist, and initiate a RM operation.

Associated revisions

Revision caab59b0
Added by Ruben S. Montero over 7 years ago

bug #1295: If an image is successfully CP/CLONE/MKFS, but it no longer exists log messages is generated to check the datastore

Revision 9ae67657
Added by Ruben S. Montero over 7 years ago

bug #1295: If an image is successfully CP/CLONE/MKFS, but it no longer exists log messages is generated to check the datastore
(cherry picked from commit caab59b038554d8c8d78d579e4834973a456a2e5)

History

#1 Updated by Ruben S. Montero over 7 years ago

  • translation missing: en.field_story_points set to 0

#2 Updated by Ruben S. Montero over 7 years ago

  • Target version changed from Release 3.8 to Release 3.6

#3 Updated by Ruben S. Montero over 7 years ago

  • Assignee changed from Carlos Martín to Ruben S. Montero

#4 Updated by Ruben S. Montero over 7 years ago

  • Status changed from New to Assigned

#5 Updated by Ruben S. Montero over 7 years ago

  • Status changed from Assigned to Closed
  • Resolution set to fixed

Added an error message if an image is successfully CP/CLONE/MKFS, but it no longer exists. Recovery actions are not automatically triggered to check datastore state.

Also available in: Atom PDF