We have separated foreman-debug command out of the foreman RPM package, it's now distributed separately (in foreman-debug subpackage) and by default it will be installed on all Capsule servers.
Since sosreport already contains foreman-debug plugin
there is no need of any changes in sosreport I believe. When sos is executed on Satellite 6 main node, it calls foreman-debug to collect additional data. When sos is executed on Capsule node, it does the same from now on.
I suggest to close this ticket.
To make this clear, the original foreman-debug command was capable of collecting information from foreman-proxy, the component that runs on Capsule server. In the upstream, usual deployment is to have the first proxy on the same server.
By installing the script on both Satelilite 6 and Capsule servers, we now collect all the relevant information. Both commands are the same with same (unchanged) options, so there is no need of changing anything in the sos report.
This bug is still required: the current foreman plugin only checks for the 'foreman' package.
Oh haven't realized that you check against RPM packages. I was under impression that script is enough. Sure, that makes sense. FYI I issued an upstream change, this is the desired state now (and for Satellite 6.1 as well):
Upstream PR https://github.com/sosreport/sos/pull/489
Upstream commit: https://github.com/sosreport/sos/commit/5cc06136d68536b806ce09ce61f800d9a7938790
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.