How to resolve prereq connectivity check failure on OpenShift 4.16-4.18

Resolve prerequisite connectivity check failures on OpenShift 4.16-4.18 control-plane nodes.

When running Automation Suite prerequisites (uipathctl prereq run) on an OpenShift cluster (versions 4.16-4.18), the cluster connectivity check can fail on certain nodes with the following error:

time="2025-07-22T13:51:02Z" level=info msg="Wizard is running on :8080"
Error: listen failed with error: listen tcp :8080: bind: address already in use

The error typically occurs only on control-plane nodes.

To address this issue, you can use one of the following workaround options:

• Run prereqs on worker nodes only.

  To avoid scheduling prereq pods on control-plane nodes, you must apply node labels to target worker nodes only. You must update input.json to include the node_labels section, as shown in the following example:

  "node_labels": {
    "node-role.kubernetes.io/worker": ""
  }
  

  This ensures that all prerequisite checks, including connectivity, are executed only on worker nodes and not on control-plane nodes where the conflict occurs.

• Skip the connectivity check. If targeting specific node roles is not possible (when nodes are configured with multiple roles), you must run the prereq command excluding the connectivity check:

  uipathctl prereq run --excluded CONNECTIVITY