Skip to content

CI: Bump -rcd wait timeout #2745

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
gavin-stackrox merged 1 commit into from
Aug 23, 2022
Merged

CI: Bump -rcd wait timeout #2745

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion deploy/common/k8sbased.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -371,7 +371,11 @@ function launch_central {
# On some systems there's a race condition when port-forward connects to central but its pod then gets deleted due
# to ongoing modifications to the central deployment. This port-forward dies and the script hangs "Waiting for
# Central to respond" until it times out. Waiting for rollout status should help not get into such situation.
kubectl -n stackrox rollout status deploy/central --timeout=6m
rollout_wait_timeout="3m"
if [[ "${IS_RACE_BUILD:-}" == "true" ]]; then
rollout_wait_timeout="9m"
fi
kubectl -n stackrox rollout status deploy/central --timeout="$rollout_wait_timeout"

# if we have specified that we want to use a load balancer, then use that endpoint instead of localhost
if [[ "${LOAD_BALANCER}" == "lb" ]]; then
Expand Down