Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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.

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35346 has been resolved.

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.

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