Bug #2466

after upgrade to opennebula 4.4, i cant deploy new vm‏

Added by novid Agha Hasani about 6 years ago. Updated about 6 years ago.

Status:ClosedStart date:11/17/2013
Priority:NormalDue date:
Assignee:Daniel Molina% Done:

100%

Category:Sunstone
Target version:Release 4.4
Resolution:worksforme Pull request:
Affected Versions:OpenNebula 4.4

Description

after upgrade to opennebula 4.4 beta (for ubuntu 13.04), I get permanently an error message when deploying new vm within sunstone

the sunstone's error is: Wrong type NilClass. Not allowed!

vm's id is 133

related log is very low and i cant found problem of them...

log's output from oned.log


Sun Nov 17 03:30:45 2013 [ReM][D]: Req:9600 UID:0 ImagePoolInfo result SUCCESS, "<IMAGE_POOL><IMAGE><..." 
Sun Nov 17 03:30:46 2013 [ImM][I]: --Mark--
Sun Nov 17 03:30:47 2013 [ReM][D]: Req:5632 UID:0 VirtualMachineInfo invoked, 133
Sun Nov 17 03:30:47 2013 [ReM][D]: Req:5632 UID:0 VirtualMachineInfo result SUCCESS, "<VM><ID>133</ID><UID..." 
Sun Nov 17 03:30:48 2013 [ReM][D]: Req:928 UID:0 ClusterPoolInfo invoked
Sun Nov 17 03:30:48 2013 [ReM][D]: Req:928 UID:0 ClusterPoolInfo result SUCCESS, "<CLUSTER_POOL><CLUST..." 

and /var/log/one/133.log is empty!

all previous vm correctly work, I even migrate them between all host, just i cant deploy new vm to specific host

I think so, error is related by ruby,isn't it?


Related issues

Related to Bug #2480: "Wrong type NilClass. Not allowed!" when deploying VMs in... Closed 11/20/2013

History

#1 Updated by Ruben S. Montero about 6 years ago

  • Assignee set to Daniel Molina

#2 Updated by Daniel Molina about 6 years ago

  • Status changed from Pending to Closed
  • % Done changed from 0 to 100
  • Resolution set to worksforme

Also available in: Atom PDF