Project

General

Profile

Actions

Bug #9704

closed

Network label is unchanged on additional network interfaces with VMware templates

Added by Bryan Kearney about 9 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Compute resources - VMware
Target version:
Difficulty:
Triaged:
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 3 (0 open3 closed)

Related to Foreman - Bug #9705: Disk sizes specified not used in VMware image provisioningClosedIvan Necas03/10/2015Actions
Related to Foreman - Bug #5630: VmWare clone from template fails if Network Adator has labels in VmWareClosed05/08/2014Actions
Blocked by Foreman - Refactor #10997: Update fog to 1.33.0ClosedDominic Cleal07/03/2015Actions
Actions #1

Updated by Bryan Kearney about 9 years ago

  • Bugzilla link set to 1197156
Actions #2

Updated by Bryan Kearney about 9 years ago

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

Updated by Dominic Cleal about 9 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
Actions #4

Updated by Ivan Necas almost 9 years ago

  • Status changed from New to Assigned
  • Assignee set to Ivan Necas
Actions #5

Updated by The Foreman Bot almost 9 years ago

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

Updated by Dominic Cleal over 8 years ago

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

Updated by Dominic Cleal over 8 years ago

Actions #8

Updated by Dominic Cleal over 8 years ago

  • translation missing: en.field_release set to 63
Actions #9

Updated by Ivan Necas over 8 years ago

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

Also available in: Atom PDF