ci: bump enterprise deploy timeout to 15m (openshift flake investigation)#619
Closed
svietry wants to merge 1 commit into
Closed
ci: bump enterprise deploy timeout to 15m (openshift flake investigation)#619svietry wants to merge 1 commit into
svietry wants to merge 1 commit into
Conversation
svietry
force-pushed
the
sv/openshift-ci-timeout
branch
3 times, most recently
from
7ecb261 to
c7bc7d3
Compare
The openshift compatibility-matrix job times out deploying enterprise at helm's default 5m --wait; the stack needs ~6m to become ready on OKD. Bump --timeout to 15m. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: Shari Vietry <shari.vietry@gmail.com>
svietry
force-pushed
the
sv/openshift-ci-timeout
branch
from
c7bc7d3 to
d506a50
Compare
There was a problem hiding this comment.
Pull request overview
This PR updates the OpenShift CI workflow to reduce flakes in the “Deploy enterprise” step by extending Helm’s wait timeout when installing the published anchore/enterprise chart, as part of investigating slow readiness on OKD/OpenShift.
Changes:
- Increase Helm install wait timeout for enterprise deploys to 15 minutes (OpenShift and non-OpenShift branches).
- Update the inline version comments for the Replicated cluster create/remove actions to
v1.16.2(commit pin unchanged).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+140
to
144
| helm install enterprise anchore/enterprise --namespace anchore -f stable/anchore-admission-controller/ci/enterprise-openshift-vals.yaml --wait --timeout 15m | ||
| else | ||
| echo "Installing enterprise" | ||
| helm install enterprise anchore/enterprise --namespace anchore -f stable/anchore-admission-controller/ci/enterprise-vals.yaml --wait | ||
| helm install enterprise anchore/enterprise --namespace anchore -f stable/anchore-admission-controller/ci/enterprise-vals.yaml --wait --timeout 15m | ||
| fi |
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.
Purpose (draft / investigation)
The Compatibility Matrix
test (openshift, 4.18.0-okd)job has been failing on every PR that touches an enterprise-related chart (#617 k8s-inventory, #618 admission controller), while gke/aks and all kind tests pass. The failure is always in the Deploy enterprise step deploying the publishedanchore/enterprisechart, hitting helm's default 5-minute--waitdeadline:Error: INSTALLATION FAILED: timed out waiting for the conditionunexpected error when reading response body ... context deadline exceededThis is unrelated to the chart bumps in those PRs — it's the enterprise stack not reaching Ready within 5m on OKD.
Change
--timeout 15mto the enterprisehelm install --wait(both openshift + non-openshift branches) to rule out slow pod startup on OKD.kubectl get pods -o wide,describe pods, and namespace events so the actual stuck pod is visible (today the step dies before any diagnostics run).This branch is based on the k8s-inventory bump so the workflow's path/enterprise-required gates actually trigger the openshift job.
Outcome to watch
🤖 Generated with Claude Code