Bug 1986467

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

After correcting a manifest (ref bz 1965023) for receptor to connect properly, the manifest information is not updated 


Running the cloud connector playbook again will correct the certs in /etc/receptor/rh_accountnumber/ but the service still shows failures:
~~~
● receptor - Receptor Node for rh_accountnumber
   Loaded: loaded (/etc/systemd/system/receptor@.service; enabled; vendor preset: disabled)
   Active: active (running) since Mon 2021-04-05 06:11:07 EDT; 1 months 21 days ago
 Main PID: 1287 (receptor)
   CGroup: /system.slice/system-receptor.slice/receptor
           └─1287 /usr/bin/python3 /usr/bin/receptor -c /etc/receptor/rh_accountnumber/receptor.conf -d /var/data/receptor/rh_accountnumber node
                                                                                                                                                                                              
May 27 11:19:52 hostname.example.com receptor[1287]: aiohttp.client_exceptions.WSServerHandshakeError: 403, message='Invalid response status', url=URL('wss://cert.cloud.redhat.com/wss/
receptor-controller/gateway')
May 27 11:19:57 hostname.example.com receptor[1287]: ERROR 2021-05-27 11:19:57,122 aa4c5445-c8a0-4170-874b-45ed889d7a40 ws ws.connect
May 27 11:19:57 hostname.example.com receptor[1287]: Traceback (most recent call last):
May 27 11:19:57 hostname.example.com receptor[1287]: File "/usr/lib/python3.6/site-packages/receptor/connection/ws.py", line 53, in connect
May 27 11:19:57 hostname.example.com receptor[1287]: proxy=proxy, proxy_auth=proxy_auth
May 27 11:19:57 hostname.example.com receptor[1287]: File "/usr/lib64/python3.6/site-packages/aiohttp/client.py", line 1012, in __aenter__
May 27 11:19:57 hostname.example.com receptor[1287]: self._resp = await self._coro
May 27 11:19:57 hostname.example.com receptor[1287]: File "/usr/lib64/python3.6/site-packages/aiohttp/client.py", line 738, in _ws_connect
May 27 11:19:57 hostname.example.com receptor[1287]: headers=resp.headers)
May 27 11:19:57 hostname.example.com receptor[1287]: aiohttp.client_exceptions.WSServerHandshakeError: 403, message='Invalid response status', url=URL('wss://cert.cloud.redhat.com/wss/receptor-controller/gateway')
~~~

First I tried removing all content in /var/data/receptor and then in /etc/receptor, but the service still fails after these. Disabling the service with `systemctl disable --now receptor` and running the playbook after now allows the service to run without error:
~~~
● receptor - Receptor Node for rh_accountnumber
   Loaded: loaded (/etc/systemd/system/receptor@.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2021-05-27 11:23:20 EDT; 26s ago
 Main PID: 12049 (receptor)
   CGroup: /system.slice/system-receptor.slice/receptor
           └─12049 /usr/bin/python3 /usr/bin/receptor -c /etc/receptor/rh_accountnumber/receptor.conf -d /var/data/receptor/rh_accountnumber node

May 27 11:23:20 hostname.example.com systemd[1]: Started Receptor Node for rh_accountnumber.
~~~

So it looks like after corrections are made to receptor configs or config files it doesn't restart after those changes.