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.
Bug 2122175 - Can't assign different networks on 2+ NICs with vNIC profiles selected
Summary: Can't assign different networks on 2+ NICs with vNIC profiles selected
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - RHEV
Version: 6.10.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: 6.11.3
Assignee: satellite6-bugs
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-29 12:41 UTC by Odilon Sousa
Modified: 2022-09-28 16:28 UTC (History)
9 users (show)

Fixed In Version: foreman-3.1.1.23-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2036151
Environment:
Last Closed: 2022-09-28 16:28:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 35346 0 Normal Closed Can't assign different networks on 2+ NICs with vNIC profiles selected 2022-08-29 12:42:11 UTC
Red Hat Product Errata RHBA-2022:6743 0 None None None 2022-09-28 16:28:59 UTC

Comment 3 Lukáš Hellebrandt 2022-09-12 12:03:52 UTC 
Verified with Sat 6.11.3 snap 1.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 4 wclark 2022-09-14 16:52:10 UTC 
Hotfix RPMs are available for this BZ for Satellite 6.11.2 on RHEL7 and Satellite 6.11.2 on RHEL8

The Hotfix RPMs are too large to be provided as a Bugzilla attachment. Please open a case with Red Hat Technical Support to request them.

INSTALL INSTRUCTIONS (Satellite 6.11.2 on RHEL7):

1. Take a complete backup or snapshot of Satellite 6.11.2 server

2. Obtain the Hotfix RPM for Satellite 6.11.2 on RHEL7 from Red Hat Technical Support and copy it to Satellite server

3. # yum install ./foreman-3.1.1.22-2.HOTFIXRHBZ2122175.el7sat.noarch.rpm --disableplugin=foreman-protector

4. # satellite-maintain service restart

INSTALL INSTRUCTIONS (Satellite 6.11.2 on RHEL8):

1. Take a complete backup or snapshot of Satellite 6.11.2 server

2. Obtain the Hotfix RPM for Satellite 6.11.2 on RHEL8 from Red Hat Technical Support and copy it to Satellite server

3. # dnf install ./foreman-3.1.1.22-2.HOTFIXRHBZ2122175.el8sat.noarch.rpm --disableplugin=foreman-protector

4. # satellite-maintain service restart
Comment 11 errata-xmlrpc 2022-09-28 16:28:48 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 (Satellite 6.11.3 Async Bug Fix Update), 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/RHBA-2022:6743
Note You need to log in before you can comment on or make changes to this bug.