Bug 1824819

Summary:	Receptor does not start after Satellite machine reboot
Product:	Red Hat Satellite	Reporter:	Marek Hulan <mhulan>
Component:	RH Cloud - Cloud Connector	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Lukáš Hellebrandt <lhellebr>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	6.7.0	CC:	ahumbe, aruzicka, bkearney, mmccune
Target Milestone:	6.8.0	Keywords:	PrioBumpField, PrioBumpGSS, PrioBumpPM, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ansiblerole-satellite-receptor-installer-0.6.5	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-06-09 08:52:48 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:
Embargoed:

Description Marek Hulan 2020-04-16 13:59:01 UTC

Description of problem:

The ansible role for configuring the cloud connector does not enable the systemd service correctly

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

6.7.0

How reproducible:

100%

Steps to Reproduce:
1. configure the cloud connector
2. restart satellite machine

Actual results:

cloud connector (receptor) is inactive - systemctl status 'receptor@all'

Expected results:

it should be active
Additional info:

Comment 7 Lukáš Hellebrandt 2020-05-22 08:54:28 UTC

I believe this is a duplicate of bug 1832594 which has been verified already in 6.7.1.