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:
User can configure networking interfaces when creating a new host that will be provisioned but the configuration is not applied during provisioning
Version-Release number of selected component (if applicable):
How reproducible:
always
Steps to Reproduce:
1. add new host with at least one more managed network interface
2. let the host provision
3. check whether it created corresponding file in /etc/sysconfig/network-scripts
Actual results:
no config file was created
Expected results:
config file is created according to config in Satellite
Additional info:
verified with:
sat6.1 beta snap6 compose2 (Satellite-6.1.0-RHEL-6-20150311.1).
now we have kickstart_networking_setup snippet, which is being used by "Katello Kicstart default" provisioning template. That does all the magic and configures the networking on provision host.
I tried alias/bond and vlan interfaces.. for all interfaces, I can see generated config files on provisioned host. Please see the screenshot for vlan interface file.
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-2015:1592