Bug #4610

Boot order should checked VMs with a wrong boot order ends in a boot failure state

Added by Ruben S. Montero over 4 years ago. Updated over 4 years ago.

Status:ClosedStart date:06/28/2016
Priority:NormalDue date:
Assignee:Ruben S. Montero% Done:

100%

Category:Core & System
Target version:Release 5.0.2
Resolution:fixed Pull request:
Affected Versions:OpenNebula 5.0

Associated revisions

Revision e71b23a4
Added by Carlos Martín over 4 years ago

Bug #4610: Check boot order contents

Revision 8529d130
Added by Carlos Martín over 4 years ago

Bug #4610: Check boot order contents

(cherry picked from commit e71b23a4e7ebda1335cb91f212965315d098eebf)

Revision 1c3881c6
Added by Carlos Martín over 4 years ago

Bug #4610: Check memory value in KB

Revision 1d6e8e5b
Added by Carlos Martín over 4 years ago

Bug #4610: Check memory value in KB

(cherry picked from commit 1c3881c6c6e22c2d12656099fc22a528bc102070)

History

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

This issue is also to check MEMORY parsing, see here

https://forum.opennebula.org/t/unable-to-start-vm/2472/1

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

  • Target version set to Release 5.2

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

  • Target version changed from Release 5.2 to Release 5.0.2

#4 Updated by Carlos Martín over 4 years ago

  • % Done changed from 0 to 100

#5 Updated by Jaime Melis over 4 years ago

  • Assignee set to Ruben S. Montero

Review

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

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

Also available in: Atom PDF