Bug 1824819 - Receptor does not start after Satellite machine reboot
Summary: Receptor does not start after Satellite machine reboot
Keywords:
Status: CLOSED DUPLICATE of bug 1832594
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: RH Cloud - Cloud Connector
Version: 6.7.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: 6.8.0
Assignee: satellite6-bugs
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-16 13:59 UTC by Marek Hulan
Modified: 2020-06-09 08:52 UTC (History)
4 users (show)

Fixed In Version: ansiblerole-satellite-receptor-installer-0.6.5
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-09 08:52:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github project-receptor satellite-receptor-installer pull 13 0 None closed Add [Install] section to receptor@.service 2020-07-23 15:29:05 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.