Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Installing a Receptor through the Configure Cloud Connector job template installs it and starts the service. However, the init file doesn't have the [Install] section and consequently, the service can't be enabled. That means the Receptor won't run after restart.

Version-Release number of selected component (if applicable):
6.7 GA (new feature)

How reproducible:
Deterministic

Steps to Reproduce:
1. Run Configure Cloud Connector job template
2. Reboot the machine

Actual results:
Receptor service stopped

Expected results:
Receptor service started, enabled

Upstream PR https://github.com/project-receptor/satellite-receptor-installer/pull/13 was merged, moving to POST. Requesting this for 6.7.z, as it is quite important and has literally no chance of breaking anything

Verified with Sat 6.8 snap 8.0 using reproducer from OP.

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 (Important: Satellite 6.8 release), 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/RHSA-2020:4366