Repository navigation
fix: retry HyperConverged apply through HCO webhook outages - #201
Merged
Merged
Conversation
The 'Create the HyperConverged instance' task applies the HyperConverged CR immediately after the kubevirt-hyperconverged CSV is subscribed. While the operator is still rolling out, the HCO conversion webhook (hco-webhook-service:4343) is not yet serving, so the apply fails with: conversion webhook for hco.kubevirt.io/v1, Kind=HyperConverged failed: Post "https://hco-webhook-service.openshift-cnv.svc:4343/convert": connect: connection refused (HTTP 500) #200 added retry/until to the subsequent read ('Wait until HyperConverged is installed') but left the apply itself unprotected, so a webhook outage during the apply still fails the deploy outright. Add the same retry/until to the apply, reusing the existing hco_wait_retries/hco_wait_delay vars. Observed intermittently on the RHACS CNV demo (rhacs-demo-cnv); the operator took ~11 min to reach CSV Succeeded, and the apply landed in that window.
rhjcd
requested review from
fridim,
rut31337,
stencell and
wkulhanek
as code owners
November 11, 2026 01:44
andrew-jones
approved these changes
Nov 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The
Create the HyperConverged instancetask inocp4_workload_openshift_virtualizationapplies the HyperConverged CR right after thekubevirt-hyperconvergedCSV is subscribed. While the operator is still rolling out, the HCO conversion webhook (hco-webhook-service:4343) is not yet serving, so the apply fails with:#200 (GPTEINFRA-18460) added
retry/untilto the subsequent read (Wait until HyperConverged is installed) but left the apply unprotected. A webhook outage during the apply still fails the deploy outright.Fix
Add the same
register+until: is succeeded+retries/delayto the apply task, reusing the existingocp4_workload_openshift_virtualization_hco_wait_retries/_hco_wait_delaydefaults (120 × 10s). No new variables.Evidence
Reproduced on the RHACS CNV demo (
rhacs-demo-cnv) on OCP 5.0.1: the cluster and operators installed cleanly (CSVkubevirt-hyperconverged-operator.v5.0.0Succeeded,rhbk-operatorSucceeded), but the HyperConverged apply landed during the ~11-min operator rollout window (hco-webhook pod up 23:40:15, CSV Succeeded 23:51:51, apply failed 23:50:14) and 500'd. On the live cluster afterward the webhook endpoint (10.235.0.16:4343) was serving normally and the HyperConverged CR was healthy — confirming a pure readiness race, not an OCP-version or catalog issue.Refs RHDPOPS-24698, RHDPSPPT-1388. Complements #200.