Project

General

Profile

Actions

Bug #2719

closed

VMWare Compute Resource, "Hosts/<hostanme>/edit/Virtual Machine" shows wrong Network for the the vm

Added by Peter Gustafsson almost 11 years ago. Updated about 7 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Compute resources - VMware
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

When creating a vm using vmware compute resource the vm is created ok, but if i later edit the vm and select Virtual Machine tab it shows wrong network for the vm in the Network field.

Br, Peter


Files

vmware-host-create.png View vmware-host-create.png 138 KB Ronny M, 06/27/2013 02:56 PM
created-host-in-vmware.png View created-host-in-vmware.png 47 KB Ronny M, 06/27/2013 02:56 PM
vmware-host-edit.png View vmware-host-edit.png 121 KB Ronny M, 06/27/2013 02:56 PM
production.log production.log 87.3 KB Ronny M, 06/27/2013 02:56 PM

Updated by Ronny M almost 11 years ago

Have same issue.

My setup:
VMWare Esxi 5.0.0 managed by VSphere (VMware vCenter Server 5.0.0.16964)
CentOS release 6.2 (Final)
Foreman 1.2 RC3

Attached files:
host-create.png (screendump, just before I hit submit, with selected network: dvPortGroup)
created-host-in-vmware.png (screendump, shows dvPortGroup (dvSwitch2) in created vm)
vmware-host-edit.png (screendump, shows network changed from dvPortGroup to "VM Network" when it edit host)
production.log (debug-log, for create and edit actions)

Actions #2

Updated by Peter Gustafsson over 10 years ago

it is possible to prioritize this bug ? because it creates confusion for the users of foreman (When using vmware) they think vm's is located on wrong network and it also causes clone of an vm to fail.

Br, Peter

Actions #3

Updated by Lukas Zapletal over 10 years ago

  • Description updated (diff)
  • Target version set to 1.3.0

Hello, I can assign it to 1.3 but I am afraid we have too many bugs there already. Not sure if we are able to pick it up.

Do you have a patch or something you can contribute? That would help a lot speeding up things :-)

Dev freeze is in two weeks! If you are able to submit some code, do it quick please.

Actions #4

Updated by Lukas Zapletal over 10 years ago

  • Target version deleted (1.3.0)
Actions #5

Updated by Dominic Cleal over 9 years ago

  • Category changed from Compute resources to Compute resources - VMware
Actions #6

Updated by Anonymous almost 8 years ago

what's the status here with newer foreman releases?

Actions #7

Updated by Anonymous about 7 years ago

  • Status changed from New to Rejected

no reaction, closing

Actions

Also available in: Atom PDF