Bug 1371883

Summary:	goferd shall not start when connected to RHN directly
Product:	Red Hat Satellite	Reporter:	Peter Vreman <peter.vreman>
Component:	katello-agent	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	high
Version:	6.2.0	CC:	bbuckingham, bkearney, cduryee, dirk.deimeke, egolov, jcallaha, jortel, mhrivnak, swadeley
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-08-02 20:57:52 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	1122832

Description Peter Vreman 2016-08-31 11:02:53 UTC

Description of problem:
The goferd is flooding the syslog when a node is connected directly to RHN. It will then try to connect to proton+amqps://subscription.rhsm.redhat.com:5647 which is ofcourse not working.

Aug 31 10:48:54 li-lc-1578 goferd: [INFO][worker-0] gofer.messaging.adapter.connect:28 - connecting: proton+amqps://subscription.rhsm.redhat.com:5647
Aug 31 10:48:55 li-lc-1578 goferd: [INFO][worker-0] gofer.messaging.adapter.proton.connection:87 - open: URL: amqps://subscription.rhsm.redhat.com:5647|SSL: ca: /etc/rhsm/ca/redhat-uep.pem|key: None|certificate: /etc/pki/consumer/bundle.pem|host-validation: None
Aug 31 10:48:55 li-lc-1578 goferd: [INFO][worker-0] root:490 - connecting to subscription.rhsm.redhat.com:5647...
Aug 31 10:49:58 li-lc-1578 goferd: [INFO][worker-0] root:532 - Disconnected
Aug 31 10:49:58 li-lc-1578 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
Aug 31 10:49:58 li-lc-1578 goferd: [INFO][worker-0] gofer.messaging.adapter.connect:35 - retry in 106 seconds


# subscription-manager config
[server]
   hostname = [subscription.rhsm.redhat.com]
   insecure = [0]
   port = [443]
   prefix = [/subscription]
   proxy_hostname = fibsproxydev.hag.hilti.com
   proxy_password = []
   proxy_port = 8080
   proxy_user = []
   ssl_verify_depth = [3]

[rhsm]
   baseurl = [https://cdn.redhat.com]
   ca_cert_dir = [/etc/rhsm/ca/]
   consumercertdir = [/etc/pki/consumer]
   entitlementcertdir = [/etc/pki/entitlement]
   full_refresh_on_yum = [0]
   manage_repos = [1]
   pluginconfdir = [/etc/rhsm/pluginconf.d]
   plugindir = [/usr/share/rhsm-plugins]
   productcertdir = [/etc/pki/product]
   repo_ca_cert = /etc/rhsm/ca/redhat-uep.pem
   report_package_profile = [1]

[rhsmcertd]
   autoattachinterval = [1440]
   certcheckinterval = [240]

[] - Default value in use


The goferd shall be used only as client for connecting to a Satellite and there not starting when the node is connected to RHN directly. This situation can be detected in the goferd on e.g. the wellknown hostname *.rhsm.redhat.com or the ca_cert being redhat-uep.pem instead of katello-server-ca.pem when connected to a Satellite


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


How reproducible:


Steps to Reproduce:
1. Connect to RHN directly
2. Start goferd
3.

Actual results:
goferd tries to connect to subscription.rhsm.redhat.com

Expected results:
goferd fails not start

Additional info:

Comment 4 Bryan Kearney 2018-08-02 20:57:52 UTC

Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.