Description of problem:

The upcoming upgrade from Satellite 6.2 to 6.3 rises the question about the compatibility and supportability of the Satellite / Capsules and the Client Tools.

While Satellite and Capsules must match [1] by definition, the situation with the client tools is unclear. In an ideal world the clients would be independent or at least upwards compatible (Satellite / Capsule on 6.3, clients on 6.2) until the next rollout of patches is executed. In a typical enterprise environment this mix will persists for months.

    [1] https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html/installation_guide/upgrading_satellite_server_and_capsule_server#upgrading_between_minor_versions

Version-Release number of selected component (if applicable):

Satellite 6.2 Client Tools

How reproducible:

always

Steps to Reproduce:
1. Upgrade Satellite / Capsule
2. Bundle Client tools for the next content host upgrade

Actual results:

Functionality and support state unclear.

Expected results:

One y version back is fully supported for katello-agent, katello-host-tools and Puppet, optionally also OpenScap.

Additional info:

This BZ might need further splits to address the individual tools independently. It's not expected that the command line tools like hammer are backward compatible, but the tools installed on a content host should be.