Project

General

Profile

Actions

Bug #1948

closed

VMware creation: vm with multiple disks fail

Added by Siert Z. about 12 years ago. Updated almost 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
VM management
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

While testing the https://github.com/ohadlevy/foreman.git branch vmware (cloned @ 15th november 2012) I get the following error when creating a VM with multiple harddisks:

Oops, we're sorry but something went wrong

x failed to create vm: InvalidDeviceSpec: Invalid configuration for device '3'.
If you feel this is an error with Foreman itself, please open a new issue with Foreman ticketing system, You would probably need to attach the Full trac>

RbVmomi::Fault
failed to create vm: InvalidDeviceSpec: Invalid configuration for device '3'.
lib/foreman/model/vmware.rb:73:in `create_vm'
app/controllers/compute_resources_vms_controller.rb:18:in `create'

Files

add_disk_failure.txt add_disk_failure.txt 14.2 KB Siert Z., 11/23/2012 02:58 PM
fulltrace_disk.txt fulltrace_disk.txt 14.2 KB trace reported in webui Siert Z., 12/18/2012 11:30 AM
parameters_disk.txt parameters_disk.txt 32 KB parameters passed to foreman Siert Z., 12/18/2012 11:30 AM
Actions #1

Updated by Sam Kottler about 12 years ago

  • Assignee set to Ohad Levy
Actions #2

Updated by Siert Z. about 12 years ago

Attached a full trace.

Actions #3

Updated by Ohad Levy about 12 years ago

can you attach foreman log it self? I need the parameters passed

thanks!

Actions #4

Updated by Sam Kottler about 12 years ago

  • Status changed from New to Need more information
  • Assignee changed from Ohad Levy to Sam Kottler

Siert, can you provide the log that Ohad asked for? I'm going to work on this issue, but the params are always helpful :-)

Actions #6

Updated by Ohad Levy almost 12 years ago

  • Status changed from Need more information to Ready For Testing
  • Assignee changed from Sam Kottler to Ohad Levy

I've found the issue and its in fog code, I've sent a pull request https://github.com/fog/fog/pull/1424 to fix it.

in the meanwhile, you can try to patch the fog code directly (as the link above)

thanks!

Actions #7

Updated by Ohad Levy almost 12 years ago

actually, it was https://github.com/fog/fog/pull/1437

and I've pushed it upstream to fog, so, once a newer fog version is out, you're covered.

Actions #8

Updated by Ohad Levy almost 12 years ago

  • Status changed from Ready For Testing to Closed
Actions

Also available in: Atom PDF