Adam, what version of receptor is needed for this?
This will need the installer role 0.6.6 (already out, upstream packaging PR available[1]) and receptor 0.6.2 which should be released any minute now. [1] - https://github.com/theforeman/foreman-packaging/pull/5179
Verified with Sat 6.7.1 snap 1. 1) Installed Satellite + Receptor 2) Let Receptor run 3) For 24 hours, ran a loop that disables and enables communication for a random time [0] 4) Stopped the loop, enabled communication 5) Scheduled a remediation through c.rh.c => Job invocation appeared in the Satellite - the Receptor was able to re-establish a communication with c.rh.c, didn't hang. [0] # blocked=0; while true; do sleep_time=$(($RANDOM % 600)); if [ $blocked -eq 1 ]; then blocked=0; echo unblocking; firewall-cmd --direct --remove-rule ipv4 filter OUTPUT 0 -p tcp -m tcp --dport=443 -j DROP; else blocked=1; echo blocking; firewall-cmd --direct --add-rule ipv4 filter OUTPUT 0 -p tcp -m tcp --dport=443 -j DROP; fi; sleep $sleep_time; done
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