Project

General

Profile

Bug #9704

Network label is unchanged on additional network interfaces with VMware templates

Added by Bryan Kearney over 4 years ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Compute resources - VMware
Target version:
Difficulty:
Triaged:
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

Customer clones host in Vmware ESX cluster from template. Template has two network interfaces. In Sat6 WebUI customer on second network interface selects some network label from the list but newly created host does not get new label but rather stays with the label from template.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
  • in VMware UI define VMware network infrastructure.
  • in VMware UI create template based on image. Image must have two or more network interfaces.
  • In Sat6 define VMware compute resource and some compute profiles * Make compute profiles using VMware template defined before
  • In satellite6 WebUI go Hosts->New Host. * Fill all needed parameters. * Select Deploy on VMware. * Select Compute Profile
  • in Virtual Machine Tab * in the Network on second interface select any of defined VLANs/Network Labels (must be queried automatically)
  • Click Submit.

Patches are available downstream


Related issues

Related to Foreman - Bug #9705: Disk sizes specified not used in VMware image provisioningClosed2015-03-10
Related to Foreman - Bug #5630: VmWare clone from template fails if Network Adator has labels in VmWareClosed2014-05-08
Blocked by Foreman - Refactor #10997: Update fog to 1.33.0Closed2015-07-03

Associated revisions

Revision 952ad8c1 (diff)
Added by Ivan Necas almost 4 years ago

Fixes #9704,#9705 - ability to customize vmware VM on image-based provisioning

Allows applying the changes form the form to the VM when cloning from
a template.

Depends on https://github.com/fog/fog/pull/3570

History

#1 Updated by Bryan Kearney over 4 years ago

  • Bugzilla link set to 1197156

#2 Updated by Bryan Kearney over 4 years ago

  • Related to Bug #9705: Disk sizes specified not used in VMware image provisioning added

#3 Updated by Dominic Cleal over 4 years ago

  • Subject changed from Network label gets unchanged on second and subsequent network interface when provisioned from VMware template to Network label is unchanged on additional network interfaces with VMware templates
  • Category set to Compute resources - VMware

#4 Updated by Ivan Necas about 4 years ago

  • Status changed from New to Assigned
  • Assignee set to Ivan Necas

#5 Updated by The Foreman Bot about 4 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/2403 added
  • Pull request deleted ()

#6 Updated by Dominic Cleal about 4 years ago

  • Related to Bug #5630: VmWare clone from template fails if Network Adator has labels in VmWare added

#7 Updated by Dominic Cleal about 4 years ago

#8 Updated by Dominic Cleal almost 4 years ago

  • Legacy Backlogs Release (now unused) set to 63

#9 Updated by Ivan Necas almost 4 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF