Bug 1928264
Summary: | Receptor service fails to run on Satellite 6.9 Beta | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Mike McCune <mmccune> |
Component: | RH Cloud - Cloud Connector | Assignee: | Adam Ruzicka <aruzicka> |
Status: | CLOSED ERRATA | QA Contact: | Lukáš Hellebrandt <lhellebr> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.9.0 | CC: | aruzicka, jaudet, jhutar, zhunting |
Target Milestone: | 6.9.0 | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | python3-receptor-satellite-1.3.1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-04-21 13:10:34 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
Mike McCune
2021-02-12 19:24:31 UTC
Fix was merged in upstream and a release is out Still reproducible on Sat 6.9 snap 13, workaround: `pip install insights-core`. How does one execute {{pip install insights-core}}? Is that command executed system-wide as root? Or in a venv? I did it system-wide as root and it worked for me. I executed `pip install insights-core && systemctl start 'receptor@*'` as root on a Satellite 6.9 snap 11 system. The receptor units successfully started, according to `systemctl status 'receptor@*'` and `journalctl --unit 'receptor@*' --follow`. The "Configure Cloud Connector" Ansible playbook was also successfully executed. Further testing will be needed to discover whether the Satellite is truly in working order, but it's looking good right now. End-to-end tests indicate that the workaround fails on snap 11. I'll continue work with a newer snap of Satellite 6.9. Verified with Sat 6.9 snap 16. Receptor installation is successful. Service starts successfuly. After a few hours of running, I don't see any related issues. Running receptor locally also doesn't show any issues: # receptor --debug --node-id controller -d /tmp/controller node --listen=receptor://0.0.0.0:8842 INFO 2021-03-09 10:10:44,775 controller entrypoints Running as Receptor node with ID: controller INFO 2021-03-09 10:10:44,776 controller controller Serving on receptor://0.0.0.0:8842 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 (Moderate: Satellite 6.9 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-2021:1313 |