USER PROBLEM
^{What is the user experiencing as a result of the bug? Include steps to reproduce.}

• Node Indexing fails in Compliance container with error:

main: 2025/03/26 10:20:31.506519 compliance.go:236: Info: Creating v4 Node Index report for node compute-259{"level":"error","version":"1.2","component":"rhel/internal/common/Updater.Get","error":"Get \"https://sensor.stackrox.svc/scanner/definitions?file=repo2cpe\": dial tcp: lookup sensor.stackrox.svc on 172.30.0.10:53: no such host","message":"error updating mapping file"}

main: 2025/03/26 10:20:31.519919 compliance.go:243: Error: Error creating node index: error indexing node: failed to run repository scanner: failed to scan repositories: rhel: unable to create a mappingFile object

utils: 2025/03/26 10:20:31.519963 intervals.go:82: Info: Next node scan in 3h50m21.802545973s 

CONDITIONS
^{What conditions need to exist for a user to be affected? Is it everyone? Is it only those with a specific integration? Is it specific to someone with particular database content? etc.}

• Fresh Helm & operator installs with Sensor installed to a non-stackrox namespace. __ 
• Upgrades of Helm & operator installs with Sensor installed to a non-stackrox namespace.

ROOT CAUSE
^{What is the root cause of the bug?}

• Programmer bug - defaulting Sensor address to `sensor.stackrox.svc` and not updating the value in the Helm charts during installation or upgrade

FIX
^{How was the bug fixed (this is more important if a workaround was implemented rather than an actual fix)?}

• See: https://github.com/stackrox/stackrox/pull/14766
• There is a workaround for 4.7.0 and 4.7.1, in which the URL could have been corrected manually by setting the env var `ROX_NODE_INDEX_MAPPING_URL` to a value containing correct Sensor host address.