Skip to content

[DEBUG][DO NOT MERGE] Add azure-ipi-peerpods-ga job for candidate422 - #82806

Closed
tbuskey wants to merge 16 commits into
openshift:mainfrom
tbuskey:260803
Closed

[DEBUG][DO NOT MERGE] Add azure-ipi-peerpods-ga job for candidate422#82806
tbuskey wants to merge 16 commits into
openshift:mainfrom
tbuskey:260803

Conversation

@tbuskey

@tbuskey tbuskey commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Add azure-ipi-peerpods-ga job to candidate422 config for peer-pod GA workload on Azure
  • 8h sleep duration for cluster debugging access
  • Uses redhat-operators catalog (GA), no RPM install
  • restrict_network_access: true for rehearsal compatibility
  • Includes install-osc-operator step and pre-chain update

Test plan

  • Rehearse azure-ipi-peerpods-ga job via /pj-rehearse
  • Verify peer-pod workload provisions correctly on Azure
  • Verify 8h wait provides cluster access

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Adds the azure-ipi-peerpods-ga periodic job to the candidate422 OpenShift CI configuration.
  • Configures Azure peer-pod GA testing with restricted network access, the redhat-operators catalog, no RPM installation, and an 8-hour debugging wait.
  • Adds the install-osc-operator step to install and configure the Sandboxed Containers Operator and peer-pod components.
  • Updates CatalogSource wait logic to use the name from the osc-config ConfigMap.
  • Adds the step to the pre-testing chain after Trustee operator installation.
  • Adds step ownership, metadata, and documentation.

Add peer-pod GA workload on Azure with 8h wait for debugging.
Uses redhat-operators catalog, no RPM install, restrict_network_access: true.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@tbuskey

tbuskey commented Aug 3, 2026

Copy link
Copy Markdown
Contributor Author

/hold

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 3, 2026
@coderabbitai

coderabbitai Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

Walkthrough

Adds a CI step and Bash script to install the OpenShift Sandboxed Containers Operator. The step configures peer-pods, waits for readiness, updates shared state, and runs before tests. Azure Kata testing now includes restricted networking and a peer-pods GA job.

Changes

Sandboxed Containers Operator installation

Layer / File(s) Summary
Step contract and pre-test wiring
ci-operator/step-registry/sandboxed-containers-operator/install-osc-operator/*, ci-operator/step-registry/sandboxed-containers-operator/pre/*
Defines the CI step, inputs, resources, documentation, ownership metadata, and pre-test chain placement.
Chart preparation and manifest rendering
ci-operator/step-registry/sandboxed-containers-operator/install-osc-operator/sandboxed-containers-operator-install-osc-operator-commands.sh
Validates settings, fetches charts, detects the cloud provider, and renders operator and operand manifests.
Operator, operand, and peer-pod installation
ci-operator/step-registry/sandboxed-containers-operator/install-osc-operator/sandboxed-containers-operator-install-osc-operator-commands.sh
Applies operator resources, waits for operator readiness, applies operands, and creates peer-pod credentials.
Readiness, shared state, and Azure coverage
ci-operator/step-registry/sandboxed-containers-operator/install-osc-operator/sandboxed-containers-operator-install-osc-operator-commands.sh, ci-operator/config/openshift/sandboxed-containers-operator/openshift-sandboxed-containers-operator-devel__downstream-candidate422.yaml
Polls KataConfig readiness, verifies peer-pod components, updates osc-config, restricts Azure Kata networking, selects scenario C00102, and adds the azure-ipi-peerpods-ga periodic job.

Estimated code review effort: 4 (Complex) | ~60 minutes

Sequence Diagram(s)

sequenceDiagram
  participant PreChain
  participant InstallScript
  participant Helm
  participant OpenShift
  participant KataConfig
  participant OSCConfig
  PreChain->>InstallScript: invoke OSC installation
  InstallScript->>Helm: fetch and render OSC charts
  InstallScript->>OpenShift: apply operator resources
  OpenShift-->>InstallScript: report operator readiness
  InstallScript->>OpenShift: apply operands and peer-pod credentials
  InstallScript->>KataConfig: poll readiness
  KataConfig-->>InstallScript: report readiness
  InstallScript->>OSCConfig: patch oscInstalled=true
Loading

Suggested reviewers: c3d, ldoktor

🚥 Pre-merge checks | ✅ 14 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Topology-Aware Scheduling Compatibility ⚠️ Warning The new step applies the external osc-operands chart without topology checks; its default KataConfig selects only node-role.kubernetes.io/worker, assuming dedicated workers. Make node selection topology-aware: query ControlPlaneTopology, avoid worker-only selection on SNO/TNF, and exclude arbiter nodes before applying KataConfig.
✅ Passed checks (14 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly identifies the main change: adding the azure-ipi-peerpods-ga job for candidate422.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed The complete PR delta changes only YAML, Markdown, JSON, and shell files; it adds no Ginkgo It, Describe, Context, or When test titles.
Test Structure And Quality ✅ Passed The PR adds YAML, metadata, documentation, OWNERS, and a Bash installation script; repository searches found no Ginkgo test files or Ginkgo constructs to assess.
Microshift Test Compatibility ✅ Passed The PR adds CI YAML, step metadata/docs, and a Bash script; repository searches found no added Ginkgo declarations or affected test files.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The pull request adds CI configuration and a Bash installation step, not Ginkgo e2e tests; no new It, Describe, Context, or When declarations are present.
Ote Binary Stdout Contract ✅ Passed The PR changes CI YAML and a Bash installation step; its ref invokes the script, and no OTE binary or Go suite setup code is added.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The PR adds YAML, shell, metadata, documentation, and job configuration only; no new Ginkgo declarations or *_test.go files were found, so this check is not applicable.
No-Weak-Crypto ✅ Passed PR additions contain no MD5, SHA1, DES, RC4, Blowfish, ECB, custom crypto, or secret comparisons; the only key generation uses Ed25519.
Container-Privileges ✅ Passed Full PR diff and changed manifests contain no privileged, hostPID/hostNetwork/hostIPC, SYS_ADMIN, root, or allowPrivilegeEscalation declarations; capabilities: intranet is a CI label.
No-Sensitive-Data-In-Logs ✅ Passed Credential values are read into variables and temporary Secret files without logging; rendered manifests now output object names only, and no shell tracing or environment dump exists.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@openshift-ci
openshift-ci Bot requested review from c3d and ldoktor August 3, 2026 12:30
@openshift-ci

openshift-ci Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tbuskey

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 3, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🧹 Nitpick comments (4)
ci-operator/step-registry/sandboxed-containers-operator/install-osc-operator/sandboxed-containers-operator-install-osc-operator-commands.sh (3)

93-100: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Remove the unused retry helper, or use it for the transient oc calls.

No call site for retry exists in this script. Dead helpers add maintenance cost. Either delete it or wrap the transient calls, such as the oc get configmap reads.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@ci-operator/step-registry/sandboxed-containers-operator/install-osc-operator/sandboxed-containers-operator-install-osc-operator-commands.sh`
around lines 93 - 100, Remove the unused retry function from the script, or
apply it consistently to transient oc calls such as the configmap reads so the
helper has an active call site.

429-436: 🎯 Functional Correctness | 🔵 Trivial | ⚡ Quick win

Select the CSV by name prefix instead of .items[0].

.items[0] returns an arbitrary CSV. The operator namespace can contain copied CSVs from other operators, and the index order is not stable. Filter for the sandboxed containers CSV.

♻️ Proposed change
   if ! wait_until "CSV Succeeded" 600 5 \
-    "[[ \"\$(oc get csv -n '${OSC_NAMESPACE}' -o jsonpath='{.items[0].status.phase}' 2>/dev/null)\" == \"Succeeded\" ]]"; then
+    "oc get csv -n '${OSC_NAMESPACE}' -o jsonpath='{range .items[?(@.spec.displayName)]}{.metadata.name}={.status.phase}{\"\\n\"}{end}' 2>/dev/null | grep -q '^sandboxed-containers-operator.*=Succeeded$'"; then
     oc get csv -n "${OSC_NAMESPACE}" -o yaml || true
     return 1
   fi
 
   local csv_name
-  csv_name=$(oc get csv -n "${OSC_NAMESPACE}" -o jsonpath='{.items[0].metadata.name}' 2>/dev/null || echo "")
+  csv_name=$(oc get csv -n "${OSC_NAMESPACE}" -o name 2>/dev/null | grep 'sandboxed-containers-operator' | head -1 || echo "")
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@ci-operator/step-registry/sandboxed-containers-operator/install-osc-operator/sandboxed-containers-operator-install-osc-operator-commands.sh`
around lines 429 - 436, Update the CSV lookups in the install flow around
wait_until and csv_name so they select the sandboxed containers CSV by its
expected name prefix rather than relying on .items[0]. Apply the same prefix
filter to both the status-phase check and metadata.name retrieval, preserving
the existing timeout, diagnostics, and failure behavior.

271-311: 🗄️ Data Integrity & Integration | 🔵 Trivial | ⚡ Quick win

Use --set-string for ConfigMap values.

helm --set coerces types and treats , and unescaped . as separators. VXLAN_PORT becomes an integer, and any value that contains a comma splits into a list. ConfigMap data requires strings. Use --set-string for all of these provider values.

♻️ Example change (apply to every value assignment in this block)
-      [[ -n "${vxlan_port}" ]] && helm_args+=("--set" "peerpods.providersConfigs.all.VXLAN_PORT=${vxlan_port}")
-      [[ -n "${proxy_timeout}" ]] && helm_args+=("--set" "peerpods.providersConfigs.all.PROXY_TIMEOUT=${proxy_timeout}")
+      [[ -n "${vxlan_port}" ]] && helm_args+=("--set-string" "peerpods.providersConfigs.all.VXLAN_PORT=${vxlan_port}")
+      [[ -n "${proxy_timeout}" ]] && helm_args+=("--set-string" "peerpods.providersConfigs.all.PROXY_TIMEOUT=${proxy_timeout}")

Note: the upstream producer sandboxed-containers-operator-peerpods-param-cm-commands.sh writes VXLAN_PORT: "9000" as a quoted string, so the string form matches the producer contract.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@ci-operator/step-registry/sandboxed-containers-operator/install-osc-operator/sandboxed-containers-operator-install-osc-operator-commands.sh`
around lines 271 - 311, Update every Helm argument assignment in the provider
configuration block, including VXLAN_PORT, PROXY_TIMEOUT, and all Azure, AWS,
and GCP ConfigMap-derived values, to use --set-string instead of --set. Preserve
the existing conditional assignments and value paths while ensuring all
ConfigMap data remains string-typed and values containing commas or dots are not
coerced or split.
ci-operator/step-registry/sandboxed-containers-operator/install-osc-operator/sandboxed-containers-operator-install-osc-operator-ref.yaml (1)

3-12: 🩺 Stability & Availability | 🔵 Trivial | ⚡ Quick win

Set an explicit step timeout for the long OSC waits.

The script adds 600s plus 600s, then KataConfig waits 7200s, so this single step can exceed the two-hour default. Add timeout: 9h0m0s so failures include command output rather than an implicit step cutoff.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@ci-operator/step-registry/sandboxed-containers-operator/install-osc-operator/sandboxed-containers-operator-install-osc-operator-ref.yaml`
around lines 3 - 12, Add an explicit timeout of 9h0m0s to the step configuration
alongside grace_period and commands, ensuring the long OSC and KataConfig waits
can complete without the default two-hour cutoff.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@ci-operator/step-registry/sandboxed-containers-operator/install-osc-operator/sandboxed-containers-operator-install-osc-operator-commands.sh`:
- Around line 376-380: Fix the ready_catalogs assignment in the catalog
readiness check so a no-match grep result remains a single numeric value; avoid
appending an extra fallback line after grep -c already prints 0. Keep the
existing total_catalogs calculation and readiness comparison unchanged.
- Around line 470-478: Restrict the operands patch around the kataconfig rename
so it changes only the targeted top-level resource name, preserving ConfigMap,
Secret, and nested name fields; use an anchored or structure-aware match tied to
the KataConfig object. Replace the full operands manifest dump after the
“Rendered operands YAML” message with an object-list-only dry-run output using
oc apply --dry-run=client -f "${operands_yaml}" -o name, and apply the same safe
object-list output to the operator manifest logging near the existing line-350
output.

In
`@ci-operator/step-registry/sandboxed-containers-operator/pre/sandboxed-containers-operator-pre-chain.yaml`:
- Line 7: Reorder the pre-chain so
sandboxed-containers-operator-install-trustee-operator runs before
sandboxed-containers-operator-install-osc-operator for existing coco jobs,
ensuring Trustee is installed before OSC KataConfig readiness is awaited.

---

Nitpick comments:
In
`@ci-operator/step-registry/sandboxed-containers-operator/install-osc-operator/sandboxed-containers-operator-install-osc-operator-commands.sh`:
- Around line 93-100: Remove the unused retry function from the script, or apply
it consistently to transient oc calls such as the configmap reads so the helper
has an active call site.
- Around line 429-436: Update the CSV lookups in the install flow around
wait_until and csv_name so they select the sandboxed containers CSV by its
expected name prefix rather than relying on .items[0]. Apply the same prefix
filter to both the status-phase check and metadata.name retrieval, preserving
the existing timeout, diagnostics, and failure behavior.
- Around line 271-311: Update every Helm argument assignment in the provider
configuration block, including VXLAN_PORT, PROXY_TIMEOUT, and all Azure, AWS,
and GCP ConfigMap-derived values, to use --set-string instead of --set. Preserve
the existing conditional assignments and value paths while ensuring all
ConfigMap data remains string-typed and values containing commas or dots are not
coerced or split.

In
`@ci-operator/step-registry/sandboxed-containers-operator/install-osc-operator/sandboxed-containers-operator-install-osc-operator-ref.yaml`:
- Around line 3-12: Add an explicit timeout of 9h0m0s to the step configuration
alongside grace_period and commands, ensuring the long OSC and KataConfig waits
can complete without the default two-hour cutoff.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 27dc1291-c4a4-4eaa-b430-3b5e0878ab22

📥 Commits

Reviewing files that changed from the base of the PR and between 93510f9 and 78b912f.

⛔ Files ignored due to path filters (1)
  • ci-operator/jobs/openshift/sandboxed-containers-operator/openshift-sandboxed-containers-operator-devel-periodics.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (7)
  • ci-operator/config/openshift/sandboxed-containers-operator/openshift-sandboxed-containers-operator-devel__downstream-candidate422.yaml
  • ci-operator/step-registry/sandboxed-containers-operator/install-osc-operator/OWNERS
  • ci-operator/step-registry/sandboxed-containers-operator/install-osc-operator/README.md
  • ci-operator/step-registry/sandboxed-containers-operator/install-osc-operator/sandboxed-containers-operator-install-osc-operator-commands.sh
  • ci-operator/step-registry/sandboxed-containers-operator/install-osc-operator/sandboxed-containers-operator-install-osc-operator-ref.metadata.json
  • ci-operator/step-registry/sandboxed-containers-operator/install-osc-operator/sandboxed-containers-operator-install-osc-operator-ref.yaml
  • ci-operator/step-registry/sandboxed-containers-operator/pre/sandboxed-containers-operator-pre-chain.yaml

@tbuskey

tbuskey commented Aug 3, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse list

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@tbuskey

tbuskey commented Aug 3, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse list

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@tbuskey

tbuskey commented Aug 3, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse list

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@tbuskey

tbuskey commented Aug 3, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate422-azure-ipi-peerpods-ga

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@tbuskey

tbuskey commented Aug 3, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse list

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

- Fix grep -c "=READY" || echo "0" producing two lines causing arithmetic
  syntax error when no CatalogSources are ready yet
- Anchor sed pattern for kataconfig rename to avoid rewriting all name: fields
- Replace cat of rendered YAML with dry-run object list to prevent leaking
  SSH keys into CI logs
- Reorder pre-chain: install-trustee-operator before install-osc-operator

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@tbuskey

tbuskey commented Aug 3, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse abort

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@tbuskey

tbuskey commented Aug 3, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate422-azure-ipi-peerpods-ga

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@tbuskey

tbuskey commented Aug 3, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse list

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@tbuskey

tbuskey commented Aug 3, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate422-azure-ipi-peerpods-ga

@tbuskey

tbuskey commented Aug 3, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse list

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

1 similar comment
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@tbuskey

tbuskey commented Aug 4, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate422-azure-ipi-peerpods-ga

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

The operator expects individual keys (AZURE_CLIENT_ID, AZURE_TENANT_ID,
etc.) not a JSON file. Use --from-literal instead of --from-file.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@tbuskey

tbuskey commented Aug 5, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate422-azure-ipi-peerpods-ga

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@tbuskey

tbuskey commented Aug 5, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate422-azure-ipi-peerpods-ga

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@tbuskey

tbuskey commented Aug 5, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse abort

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@tbuskey

tbuskey commented Aug 5, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate422-azure-ipi-peerpods-ga

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

The WAS_TRACING pattern ($false && set -x) returns exit code 1,
which set -e catches. Since the script never enables tracing,
remove the save/restore entirely.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@tbuskey: pj-rehearse could not automatically process this event because the request waited in queue for longer than 5 minutes. Use /pj-rehearse to trigger rehearsals manually.

@tbuskey

tbuskey commented Aug 5, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate422-azure-ipi-peerpods-ga

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@tbuskey

tbuskey commented Aug 5, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse abort

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

The verify_peerpod_pods() function used stale label selectors
(app=cloud-api-adaptor, app=peerpodconfig-ctrl-caa-daemon) that
don't match current OSC pod labels (name=osc-caa-ds, peer-pods-webhook).
Rather than fix the labels, remove the check entirely — KataConfig
InProgress=False already confirms the operator finished reconciling
nodes, runtime classes, and all managed pods.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@tbuskey

tbuskey commented Aug 5, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@tbuskey

tbuskey commented Aug 5, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse abort

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@tbuskey

tbuskey commented Aug 5, 2026

Copy link
Copy Markdown
Contributor Author

/pj-rehearse

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

Signed-off-by: Tom Buskey <tbuskey@redhat.com>
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@tbuskey: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate419-aro-ipi-coco N/A periodic Registry content changed
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-release-aws-ipi-peerpods N/A periodic Registry content changed
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate420-azure-ipi-peerpods N/A periodic Registry content changed
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-release-azure-ipi-coco N/A periodic Registry content changed
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate420-aws-ipi-coco N/A periodic Registry content changed
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate420-aws-ipi-peerpods N/A periodic Registry content changed
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate419-aws-ipi-coco N/A periodic Registry content changed
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate422-aro-ipi-coco N/A periodic Registry content changed
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-release-aro-ipi-coco N/A periodic Registry content changed
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate420-aro-ipi-peerpods N/A periodic Registry content changed
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate-aws-ipi-peerpods N/A periodic Registry content changed
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate417-azure-ipi-coco N/A periodic Registry content changed
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate-aws-ipi-coco N/A periodic Registry content changed
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate422-aws-ipi-coco N/A periodic Registry content changed
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate417-aws-ipi-coco N/A periodic Registry content changed
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate-aro-ipi-coco N/A periodic Registry content changed
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate419-azure-ipi-coco N/A periodic Registry content changed
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate418-aro-ipi-coco N/A periodic Registry content changed
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate422-azure-ipi-peerpods N/A periodic Registry content changed
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate418-aws-ipi-peerpods N/A periodic Registry content changed
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate417-aro-ipi-coco N/A periodic Registry content changed
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate418-azure-ipi-peerpods N/A periodic Registry content changed
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate417-azure-ipi-peerpods N/A periodic Registry content changed
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-release-azure-ipi-peerpods N/A periodic Registry content changed
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-release-azure-ipi-kata N/A periodic Registry content changed

A total of 50 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs.

A full list of affected jobs can be found here
The following jobs are not rehearsable without the network-access-rehearsals-ok, and approved labels present on this PR. This is due to the restrict_network_access field being set to false. The network-access-rehearsals-ok label can be added by any openshift org member other than the PR's author by commenting: /pj-rehearse network-access-allowed:

Test name
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate421-azure-ipi-kata
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate421-azure-ipi-peerpods
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate421-azure-ipi-coco
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate421-aro-ipi-peerpods
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate421-aro-ipi-coco
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate421-aws-ipi-peerpods
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate421-aws-ipi-coco
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@tbuskey tbuskey closed this Aug 6, 2026
@openshift-ci

openshift-ci Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

@tbuskey: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/rehearse/periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate422-aro-ipi-coco 178ce31 link unknown /pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate422-aro-ipi-coco
ci/rehearse/periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate-aro-ipi-coco 178ce31 link unknown /pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate-aro-ipi-coco
ci/rehearse/periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate-aro-ipi-peerpods 178ce31 link unknown /pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-candidate-aro-ipi-peerpods

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant