Problem Description

The install-authorino.sh script times out while waiting for Authorino pods to become ready, even though the pods are actually running successfully. The root cause is that the script searches for pods using an incorrect label selector.

Expected vs Actual Labels

Script searches for: app.kubernetes.io/name=authorino
Actual pod labels: authorino-resource=authorino, control-plane=controller-manager

The Authorino operator (v1.1.3 from Red Hat operators catalog) creates pods with different labels than what the script expects, causing the script to fail even though the deployment is successful.

Error Message

[INFO] Waiting for Authorino pods to be ready...
........................
[ERROR] Timeout waiting for Authorino pods to be ready
[ERROR] Failed to create Authorino instance

Evidence of Successful Deployment

$ oc get pods -n ros-ocp
NAME                         READY   STATUS    RESTARTS   AGE
authorino-849c6fd8cc-92dzc   1/1     Running   0          8m17s

$ oc get authorino -n ros-ocp
NAME        AGE
authorino   8m

$ oc get authorino -n ros-ocp -o jsonpath='{.items[0].status.conditions}'
[{"lastTransitionTime":"2025-11-03T21:40:34Z","reason":"Provisioned","status":"True","type":"Ready"}]

Steps to Reproduce

1. 1. Run install-authorino.sh script
      2. Script creates Authorino CR successfully
      3. Authorino operator creates pod with labels: authorino-resource=authorino
      4. Script waits for pods with label: app.kubernetes.io/name=authorino
      5. Script never finds pods and times out after 120 seconds
      6. Deployment is actually successful but script reports failure

Affected Code Locations

File: scripts/install-authorino.sh

Line 227: Pod readiness check

local ready_pods=$(oc get pods -n "$NAMESPACE" -l app.kubernetes.io/name=authorino 2>/dev/null | grep "Running" | wc -l | tr -d ' ')

Line 231: Display running pods

oc get pods -n "$NAMESPACE" -l app.kubernetes.io/name=authorino

Line 321: Verification check

local pod_count=$(oc get pods -n "$NAMESPACE" -l app.kubernetes.io/name=authorino --no-headers 2>/dev/null | wc -l | tr -d ' ')

Fix

Change all three occurrences from:

-l app.kubernetes.io/name=authorino

To:

-l authorino-resource=authorino

Workaround

The deployment actually succeeds despite the script timeout. You can verify manually:

oc get pods -n ros-ocp -l authorino-resource=authorino
oc get authorino -n ros-ocp

If both show healthy/ready status, the installation succeeded and you can proceed to the next step.

Environment Information

• Repository: ros-helm-chart
• Git Branch: main
• Git Commit: 7ff078b513b7991f558e212184ed86fae3c6742d
• Affected File: scripts/install-authorino.sh (lines 227, 231, 321)
• Authorino Operator: v1.1.3 (Red Hat tech-preview-v1 channel)
• Affected Version: IOP-POC-0.1
• Component: insights-on-prem

Severity

Medium - Script reports failure even though deployment succeeds. Causes confusion and may lead users to think installation failed when it actually completed successfully.