Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Description of problem:

When creating a new host, a predefined compute profile is selected. The defaults set in said profile for the network interface (network type, network, NIC type) aren't passed and they have to be manually set again in the Interfaces tab. Seen in profiles with both VMWare and Libvirt as compute resource.


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

6.2.7 
6.2.8


How reproducible:

Always


Steps to Reproduce:

1. Create compute profile with default values for the network interface.
2. Initiate provisioning with Hosts > New Hosts and select relevant profile.
3. Confirm wrong values in the Interfaces tab.


Actual results:

The predefined settings aren't set when selecting the profile.


Expected results:

The interface is preconfigured as per the profile.


Additional info:

http://projects.theforeman.org/issues/13980

I was able to reproduce this for primary interface on 6.2, additional interfaces seemed to be fine. This is already fixed in 6.3, moving to QE to verify.

Verified.
Version Tested: Satellite-6.3 Snap 11

Steps:
1. Create a Libvirt compute resource
2. Create a compute profile and add 2 interfaces
3. Create a host, select the compute profile
4. Go to interfaces tab and check the interfaces include a Libvirt (from profile EXAMPLE) section
5. Check the Network type, Network and NIC type are correct

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, 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-2018:0336