Description of problem:

Here in https://docs.redhat.com/en/documentation/red_hat_satellite/6.14/html-single/release_notes/index#new-features , we mention that 

As a result of an upcoming Satellite feature, hosts will now be assigned Content Views and lifecycle environments as a single unit instead of separately. Hostgroups will be required to assign both a Content View and a lifecycle environment to a host simultaneously. This ensures that a host cannot have a lifecycle environment without an associated Content View.

But we do not document the relevant code\macro changes to access those objects for the host

Due to this, if someone was using a custom kickstart and then upgrade to 6.14, they will not be able to render the provisioning template due to error 

There was an error rendering the $template_name template. undefined method '#lifecycle_environment' for Host::Managed::Jail (Host::Managed)

How reproducible:

Always 

Is this issue a regression from an earlier version:

yes but only doc steps missing 

Steps to Reproduce:

1.

2.

3.

Actual behavior:

There was an error rendering the $template_name template. undefined method '#lifecycle_environment' for Host::Managed::Jail (Host::Managed)

Expected behavior:

No such errors.  In the Post-upgrade steps of 6.14, we should document this i.e. 

Any presence of 

@host.lifecycle_environment

 should be replaced with 

@host.single_lifecycle_environment

Similarly, 

@host.content_view

 should be replaced with 

@host.single_content_view

Feel free to re-word the statements as per doc standards. Reference KB https://access.redhat.com/solutions/7052414 

Business Impact / Additional info: