Skip to content

USHIFT-3315: Increase delete openshift-ingress pod timeout #3439

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
openshift-merge-bot merged 1 commit into from
Jun 5, 2024
Merged

USHIFT-3315: Increase delete openshift-ingress pod timeout #3439

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
2 changes: 1 addition & 1 deletion test/suites/standard1/router.robot
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,7 @@ Router Disabled
[Setup] Run Keywords
... Disable Router

Run With Kubeconfig oc wait --for=delete namespace/openshift-ingress --timeout=60s
Run With Kubeconfig oc wait --for=delete namespace/openshift-ingress --timeout=300s
Copy link
Contributor

@ggiguash ggiguash Jun 5, 2024

Choose a reason for hiding this comment

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

Can you explain where we need this change? I do not remember this command expiring in MicroShift CI.

Copy link
Contributor Author

@agullon agullon Jun 5, 2024

Choose a reason for hiding this comment

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

When running RF test suite in QE environment, RF tests execution is stuck in Router Suite Teardown. This is because the pod on openshift-ingress namespace takes more than 60 seconds to be deleted, so teardown process fails and no other RF test is executed. So I tested increasing the timeout and this is issue is no longer reproducible.


Router Exposure Configuration
[Documentation] Test custom ports and custom listening addresses.
Expand Down