Bug 1166162
| Summary: | [RFE] Expose network configuration via ENC | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Bryan Kearney <bkearney> | ||||
| Component: | Configuration Management | Assignee: | Marek Hulan <mhulan> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Sachin Ghai <sghai> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.0.4 | CC: | dcleal, mhulan, riehecky, sghai, sthirugn | ||||
| Target Milestone: | Unspecified | Keywords: | FutureFeature, Triaged | ||||
| Target Release: | Unused | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | http://projects.theforeman.org/issues/2089 | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Enhancement | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-08-12 05:19:36 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Bryan Kearney
2014-11-20 13:44:20 UTC
Created from redmine issue http://projects.theforeman.org/issues/2089 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. Moving to POST since upstream bug http://projects.theforeman.org/issues/2089 has been closed ------------- Marek Hulán Applied in changeset commit:a1b2ee53189c2fdac9e643374799bf0a05957432. Taking this as related feature is already in my plate.. @Marek, hey could you please point the steps to verify this ? How can I check the network_configuration via ENC. 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. 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. Created attachment 1012164 [details]
can see n/w configuration via yaml from host details.
This bug is slated to be released with Satellite 6.1. 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 |