We don't modify platform files (such as katelloplugin.conf). Moving components to katello for handling.
1. Clean install rhvh-220.127.116.11-0.20180518.0
2. Register RHVH to RHSM
3. Check the log file /var/log/messages
Customer issue occurs.
May 23 12:19:02 dhcp-9-130 goferd: [ERROR][worker-0] gofer.messaging.adapter.connect:33 - connect: proton+amqps://subscription.rhsm.redhat.com:5647, failed: Connection amqps://subscription.rhsm.redhat.com:5647 disconnected
The bug can be reproduced from QE.
We're going to workaround on RHV-H side disabling the service / removing it form enabled services preset
moved to satellite so they can track the issue on their side while we workaround it on RHV side.
We are tracking RHV-H workaround in bug #1613231. Please keep this on gofer side and either close wontfix/notabug or solve.
Note this will be workarounded on RHV-H side but will still be an issue in RHEL hosts managed by RHV-M.
Are there any plans to fix this for a rhel based rhv host? This issue is about to turn one year old :)
*** Bug 1711320 has been marked as a duplicate of this bug. ***
*** Bug 1756792 has been marked as a duplicate of this bug. ***
The katello-agent package, which provides our goferd integration, is designed around the Satellite workflows for registering a client with Satellite and using Satellite to manage it there after. The current workflows do not provide for us to disable this by default nor is there a benefit to current workflows. Given that, and the age of this BZ I am going to opt to close wontfix at this point.
If the original use case, or any new use cases require the need to have katello-agent (the part that handles remote yum actions only) to be present on a system but not registered to Satellite actively, please re-open and outline the use case.