The cleanup worker fails when processing a private Service Cluster whose API URL is empty or missing.

This results in the following error and blocks the Service Cluster from being fully cleaned up:

E1203 04:04:13.837187       1 logger.go:188] gitlab.cee.redhat.com/service/osd-fleet-manager/internal/osdfm/internal/workers.processCleanupServiceCluster: failed to reconcile cleanup hs-sc cluster d4nodniuuibc73bm83eg status: error while checking if service cluster 'd4nodniuuibc73bm83eg' is reachable: error while pinging cluster d4nodniuuibc73bm83eg (type: hs-sc): Get "": unsupported protocol scheme ""

The failure happens because checkClusterReachable() attempts to perform an HTTP GET with an empty URL (Get ""), which causes the Go HTTP client to throw an unsupported protocol scheme error. As a result:

• processCleanupServiceCluster() returns early

• processCleanupCluster() is never executed

• The Service Cluster remains stuck in cleanup state

This commonly occurs when:

• The underlying OCM cluster was never fully provisioned

• The API URL was never populated

• The cluster resource was already deleted upstream

These clusters should be considered unreachable and allowed to proceed with cleanup instead of failing.