-
Bug
-
Resolution: Done
-
Critical
-
None
-
None
-
None
I have a Satellite 6.10 configured w/stage, and it keeps disappearing from the list of sources within 24 hours after being added.
Weirdly, even when the Satellite is absent from the list of sources:
- Hosts can still register to the satellite and run insights-client --register just fine. The hosts will subsequently appear in the CRC inventory app.
- The Satellite can still run an inventory upload.
The primary negative effects of this issue appear to be:
- Remediations that use this satellite fail, due to pre-flight checks failing.
- The satellite isn't in the list of sources, hampering visibility and troubleshooting.
I've seen this issue three times now. Re-executing the "configure cloud connector" job causes the Satellite to re-appear in the list of sources. I don't see this issue with Satellite 6.11 (w/RHC).
I'm currently seeing this issue only in stage, and not in prod. The Satellite I'm seeing this issue with is https://ci-vm-10-0-148-141.hosted.upshift.rdu2.redhat.com/. The most recent run of the "configure cloud connector" playbook reported a Satellite UUID of 67e520e0-179b-54a5-83fe-966d043c85be, and its source ID is 186466.
Slack chat reference: https://coreos.slack.com/archives/C0246P60U8H/p1657811141074279
- is related to
-
RHCLOUD-20440 Return 400 responses for IDs < 1
-
- Closed
-
-
RHCLOUD-20441 Remove the structs with ids that are then used as "where" conditions
-
- Closed
-