Bug #1237

History timers are not initialized

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

Status:ClosedStart date:04/17/2012
Priority:NormalDue date:
Assignee:Carlos Martín% Done:

0%

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

Description

Chris Johnston reports in the mailing list that simultaneous deployments can create VMs with uninitialized times.

I've been able to reproduce the bug, but only when the deployed VMs are created with "onevm create", instead of "ontemplate instantiate".

Associated revisions

Revision 05f93acb
Added by Carlos Martín over 8 years ago

Bug #1237: Disable the cache name index for the VM pool

Revision 1696bb66
Added by Ruben S. Montero over 8 years ago

bug #1237: Move access to uses_name_pool to critical section

Revision 318e874a
Added by Carlos Martín over 8 years ago

Bug #1237: Disable the cache name index for the VM pool
(cherry picked from commit 05f93acb38f17f531596629462a15b178c01a278)

Conflicts:

src/image/Image.cc

Revision 07a592e6
Added by Ruben S. Montero over 8 years ago

bug #1237: Move access to uses_name_pool to critical section
(cherry picked from commit 1696bb669ea848fba70209f146783103c0534f7e)

History

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

  • Status changed from Assigned to Closed
  • Target version set to Release 3.6
  • Resolution set to fixed

Now in master and one-3.4 branches

Also available in: Atom PDF