Project

General

Profile

Actions

Bug #26280

closed

The network used is different from the one visible in the network modal.

Added by Ondřej Ezr over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Network
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

Description of problem:
Error when creating a new Content Host using VMWare Compute Resource. The network information coming from Compute Profile appears to be correct on the webUI but when submitted generate an error (and then we are able to see a diff dvport group as expected)

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

Steps to Reproduce:
1. Create a Compute Resouce
2. Create a Compute Profile
3. Create a Hostgroup
4. Create a new Content Host and use the hostgroup

Actual results:
Seeing selected different network in the modal window, than in the network table.

Expected results:
See the same network in both - modal and the network table.

Additional info:


Related issues 3 (1 open2 closed)

Related to Foreman - Bug #26279: Foreman shows incorrect vmware interface type in network settingsNewActions
Related to Foreman - Feature #21676: Select related vmware network when selecting a subnetClosedTimo Goebel11/15/2017Actions
Related to Foreman - Bug #26307: Vmware network comming from subnet guess should not rewrite the one selected on compute profileClosedOndřej EzrActions
Actions #1

Updated by Ondřej Ezr over 5 years ago

  • Description updated (diff)
  • Bugzilla link set to 1660258

The problem relies in the magical selection of a network by function selectRelatedNetwork after triggering it on non active modal.

Actions #2

Updated by The Foreman Bot over 5 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/6552 added
Actions #3

Updated by Marek Hulán over 5 years ago

  • Related to Bug #26279: Foreman shows incorrect vmware interface type in network settings added
Actions #4

Updated by Marek Hulán over 5 years ago

  • Fixed in Releases 1.22.0 added
Actions #5

Updated by Marek Hulán over 5 years ago

  • Related to Feature #21676: Select related vmware network when selecting a subnet added
Actions #6

Updated by Anonymous over 5 years ago

  • Status changed from Ready For Testing to Closed
Actions #7

Updated by Tomer Brisker over 5 years ago

  • Category set to Network
Actions #8

Updated by Marek Hulán over 5 years ago

  • Related to Bug #26307: Vmware network comming from subnet guess should not rewrite the one selected on compute profile added
Actions

Also available in: Atom PDF