Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1166162 - [RFE] Expose network configuration via ENC
[RFE] Expose network configuration via ENC
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Configuration Management (Show other bugs)
6.0.4
Unspecified Unspecified
unspecified Severity low (vote)
: Unspecified
: Unused
Assigned To: Marek Hulan
Sachin Ghai
http://projects.theforeman.org/issues...
: FutureFeature, Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2014-11-20 08:44 EST by Bryan Kearney
Modified: 2017-02-23 15:47 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-08-12 01:19:36 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


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


External Trackers
Tracker ID Priority Status Summary Last Updated
Foreman Issue Tracker 2089 None None None 2016-04-22 11:48 EDT
Red Hat Product Errata RHSA-2015:1592 normal SHIPPED_LIVE Important: Red Hat Satellite 6.1.1 on RHEL 6 2015-08-12 05:04:35 EDT

  None (edit)
Description Bryan Kearney 2014-11-20 08:44:20 EST
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 08:44:21 EST
Created from redmine issue http://projects.theforeman.org/issues/2089
Comment 2 Bryan Kearney 2014-11-20 08:44:41 EST
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 08:52:09 EST
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 06:04:05 EST
Taking this as related feature is already in my plate..
Comment 8 Sachin Ghai 2015-03-18 07:20:38 EDT
@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 07:56:57 EDT
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 06:32:43 EDT
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 06:33:58 EDT
Created attachment 1012164 [details]
can see n/w configuration via yaml from host details.
Comment 12 Bryan Kearney 2015-08-11 09:32:39 EDT
This bug is slated to be released with Satellite 6.1.
Comment 13 errata-xmlrpc 2015-08-12 01:19:36 EDT
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.