Description of problem: Many customers using hiera have used the parameter kt_env in their hiera hierarchy. This parameter has been removed in 6.1 and should be re-added. Version-Release number of selected component (if applicable): 6.1.1 How reproducible: 100% Actual results: Parameter unavailable. Expected results: Parameter should be available.
This was removed as it was used by an internal mechanism and wasn't intended to be used by users. that said there is no reason to not include it.
Created redmine issue http://projects.theforeman.org/issues/11456 from this bug
Note that the fix for this includes the old 'kt_env' and 'kt_cv' parameters, but these should be considered deprecated and may be removed at some point in the future (likely 6.3). New ones are added which are meant for general use and should be supported long term: "lifecycle_environment" and "content_view"
Upstream bug assigned to jsherril
Hi, please provide verification steps thanks Thanks and Regards, Tazim
verification steps: 1. publish a content view to a lifecycle environment 2. Create a host on the Hosts > all hosts page (you'll likely need to create a domain for this). Make sure to select a content view and lifecycle environment when creating the host 3. After creating the host and while on the host details page click the YAML button under 'Details' in the row of four buttons on the left. 4. Notice yaml that looks like this: classes: {} parameters: puppetmaster: foo.bar.com hostgroup: testgroup234 location: Default_Location organization: The Demo Org root_pw: foreman_env: KT_The_Demo_Org_Library_Filteretest_19 owner_name: Admin User owner_email: root testin1235: aaaaaaa content_view: Filteretest kt_cv: Filteretest lifecycle_environment: Library kt_env: Library environment: KT_The_Demo_Org_Library_Filteretest_19 You should see 'kt_cv' & 'kt_env' in this list (order is not important). If you see them the bug is verified. You should also see 'lifecycle_environment' and 'content_view'.
Here's what I see: --- classes: {} parameters: puppetmaster: <EDITED> domainname: '' hostgroup: RHEL 6 x86_64 HG location: Default Location organization: RbeQr root_pw: $1$fBHSOIeR$KDjbxR5SnBz5PTBC88oYb0 puppet_ca: <EDITED> foreman_env: KT_RbeQr_Library_RHEL_6_CV_44 owner_name: Admin User owner_email: root@<EDITED> foreman_subnets: - network: 192.168.100.0 mask: 255.255.255.0 name: qe-subnet gateway: '' dns_primary: '' dns_secondary: '' from: '' to: '' boot_mode: DHCP ipam: DHCP foreman_interfaces: - mac: 52:54:00:65:30:c9 ip: 192.168.100.2 type: Interface name: attrs: {} virtual: false link: true identifier: eth0 managed: true subnet: network: 192.168.100.0 mask: 255.255.255.0 name: qe-subnet gateway: '' dns_primary: '' dns_secondary: '' from: '' to: '' boot_mode: DHCP ipam: DHCP net.iframes: '1' test.global.parameter.1: '1' kt_activation_keys: rhel6-provision-ak kt_env: Library kt_cv: RHEL_6_CV lifecycle_environment: Library content_view: RHEL_6_CV environment: KT_RbeQr_Library_RHEL_6_CV_44
Verified on Sat6.1.2-SNAP1 as per my previous comment.
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/RHBA-2015:1786