Bug 1832594

Summary: Receptor init file missing [Install] section, receptor service won't run after restart
Product: Red Hat Satellite Reporter: Mike McCune <mmccune>
Component: RH Cloud - Cloud ConnectorAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Lukáš Hellebrandt <lhellebr>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.7.0CC: aruzicka, ehelms, mhulan, psavage, zhunting
Target Milestone: 6.7.1Keywords: 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: 1828257 Environment:
Last Closed: 2020-06-08 13:18:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 3 Zach Huntington-Meath 2020-05-07 17:33:59 UTC
Adam, what's the version of receptor that is needed for this?

Comment 4 Adam Ruzicka 2020-05-07 17:42:03 UTC
Changes for this live completely in the installer role and should be available since ansiblerole-satellite-receptor-installer-0.6.5.

Comment 5 Lukáš Hellebrandt 2020-05-20 10:57:00 UTC
Verified with Sat 6.7.1. snap 1.

1) /etc/systemd/system/receptor@.service now contains [Install] section
2) "systemctl {start,stop,enable,disable} receptor@..." work, e.g.
# systemctl enable receptor@rh_1212729
Created symlink from /etc/systemd/system/multi-user.target.wants/receptor to /etc/systemd/system/receptor@.service.
3) After rebooting the system, the receptor service runs
4) Receptor's basic end-to-end scenario works

Comment 8 errata-xmlrpc 2020-06-08 13:18:03 UTC
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.

https://access.redhat.com/errata/RHBA-2020:2422

Comment 9 Marek Hulan 2020-06-09 08:52:48 UTC
*** Bug 1824819 has been marked as a duplicate of this bug. ***