Bug #5460

onedb purge-history only works with VMs with multiple history records in the body

Added by Javi Fontan over 1 year ago. Updated over 1 year ago.

Status:ClosedStart date:10/17/2017
Priority:NormalDue date:
Assignee:Javi Fontan% Done:

0%

Category:CLI
Target version:Release 5.4.3
Resolution:fixed Pull request:
Affected Versions:OpenNebula 5.4, OpenNebula 5.4.1, OpenNebula 5.4.2

Description

If the VM only contains the last history record in vm_pool it is skipped. The sequence number must be checked instead.

Associated revisions

Revision 23fe1645
Added by Javi Fontan over 1 year ago

B #5460: onedb purge-size check seq number

Revision 338fc30b
Added by Javi Fontan over 1 year ago

B #5460: onedb purge-size check seq number

(cherry picked from commit 23fe16454e700c4df1172130139b94bec435d7ed)

Revision 34db8f3b
Added by Javi Fontan over 1 year ago

B #5460: onedb purge-size check seq number

(cherry picked from commit 23fe16454e700c4df1172130139b94bec435d7ed)

History

#1 Updated by Javi Fontan over 1 year ago

  • Status changed from Pending to Closed

Fixed in one-5.4 and master branches

#2 Updated by Javi Fontan over 1 year ago

  • Resolution set to fixed

Also available in: Atom PDF