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 1166162 - [RFE] Expose network configuration via ENC
Summary: [RFE] Expose network configuration via ENC
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Configuration Management
Version: 6.0.4
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: Unspecified
Assignee: Marek Hulan
QA Contact: Sachin Ghai
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-20 13:44 UTC by Bryan Kearney
Modified: 2017-02-23 20:47 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-12 05:19:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
can see n/w configuration via yaml from host details. (51.64 KB, image/png)
2015-04-08 10:33 UTC, Sachin Ghai 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 2089 0 None None None 2016-04-22 15:48:12 UTC
Red Hat Product Errata RHSA-2015:1592 0 normal SHIPPED_LIVE Important: Red Hat Satellite 6.1.1 on RHEL 6 2015-08-12 09:04:35 UTC

Description Bryan Kearney 2014-11-20 13:44:20 UTC 
I'd like to see the hosts network information exposed as parameters in the ENC output.  Currently we have to duplicate all this information via host parameters (we use things like main_ip => 10.0.0.5, main_gateway => 10.0.0.1, main_subnet_mask => 255.255.255.0).  It would be nice to not have to duplicate all this.

Basically, everything on the subnet page would be nice to have access to from puppet classes.
Comment 1 Bryan Kearney 2014-11-20 13:44:21 UTC 
Created from redmine issue http://projects.theforeman.org/issues/2089
Comment 2 Bryan Kearney 2014-11-20 13:44:41 UTC 
I am pulling down important features from the 1.7 release. You can read more abotu this feature at 

http://theforeman.org/manuals/1.7/index.html#Releasenotesfor1.7

I believe that QE will be done by the community on this feature.
Comment 3 Bryan Kearney 2014-11-20 13:52:09 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/2089 has been closed
-------------
Marek Hulán
Applied in changeset commit:a1b2ee53189c2fdac9e643374799bf0a05957432.
Comment 7 Sachin Ghai 2015-02-13 11:04:05 UTC 
Taking this as related feature is already in my plate..
Comment 8 Sachin Ghai 2015-03-18 11:20:38 UTC 
@Marek, hey could you please point the steps to verify this ? How can I check the network_configuration via ENC.
Comment 9 Marek Hulan 2015-03-18 11:56:57 UTC 
Go to host detail page, click YAML button and check that you see keys foreman_subnets and foreman_interfaces nested under parameters.

More background: this YAML is an ENC output that puppetmaster gets from Foreman (Foreman is ENC), puppetmaster uses it to find out what puppet classes should be applied to a puppet agent (host) and what configuration values should be used. Foreman also attaches the networking info which puppet classes can use to configure the host accordingly. This networking info is available as global parameters (similar to puppet facts) so you could look at $foreman_subnets or $foreman_interfaces in your puppet manifest.
Comment 10 Sachin Ghai 2015-04-08 10:32:43 UTC 
Thanks Marek. 


Verified with snap11/RC5 (Satellite-6.1.0-RHEL-7-20150407.1). I can see the network configuration via ENC. by clicking on 'YAML button from host details page.
Comment 11 Sachin Ghai 2015-04-08 10:33:58 UTC 
Created attachment 1012164 [details]
can see n/w configuration via yaml from host details.
Comment 12 Bryan Kearney 2015-08-11 13:32:39 UTC 
This bug is slated to be released with Satellite 6.1.
Comment 13 errata-xmlrpc 2015-08-12 05:19:36 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, 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
Note You need to log in before you can comment on or make changes to this bug.