Bug 2036151

Summary: Can't assign different networks on 2+ NICs with vNIC profiles selected
Product: Red Hat Satellite Reporter: Alexey Masolov <amasolov>
Component: Compute Resources - RHEVAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Lukáš Hellebrandt <lhellebr>
Severity: high Docs Contact:
Priority: high    
Version: 6.10.1CC: ajchavan, ankulkar, ekohlvan, hlawatschek, jbhatia, orabin, osousa, pcreech
Target Milestone: 6.12.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: foreman-3.3.0.6-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2122175 (view as bug list) Environment:
Last Closed: 2022-11-16 13:33:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot none

Description Alexey Masolov 2021-12-30 03:15:36 UTC
Created attachment 1848291 [details]
screenshot

Description of problem:
If you configure a compute profile with two NICs and select different vNIC profiles for them then you can't have two different networks on the NICs. You change one and the other one gets changed automatically to the same network.

Expected results:
Able to use networks configured in vNIC profiles on multiple interfaces.

Comment 10 Bryan Kearney 2022-08-17 12:04:14 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35346 has been resolved.

Comment 14 Lukáš Hellebrandt 2022-09-09 10:32:29 UTC
Verified with Sat 6.12 snap 9.0.

Created a CR. For that CR, created a CP with two interfaces...
1) ... with the same network and with different vNICs
2) ... with different networks and different vNICs
Created a Host using that CR and CP, filling the rest of the form as necessary. The form was pre-filled correctly with networks and vNICs.
Looking through the RHEV, the VMs had correct networks and vNICs specified.

Comment 18 errata-xmlrpc 2022-11-16 13:33:03 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.12 Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:8506