Skip to content

Increase deloyment timeout in e2e to accommodate Windows deployments#1326

Merged
k8s-ci-robot merged 1 commit into
kubernetes-sigs:masterfrom
jsturtevant:windows-timeout-e2e
Apr 20, 2021
Merged

Increase deloyment timeout in e2e to accommodate Windows deployments#1326
k8s-ci-robot merged 1 commit into
kubernetes-sigs:masterfrom
jsturtevant:windows-timeout-e2e

Conversation

@jsturtevant
Copy link
Copy Markdown
Contributor

What type of PR is this?
/kind flake

What this PR does / why we need it:
The windows pod sometimes takes longer to come online. Logs indicate it pulling was still in progress.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

We could have a separate timeout for Windows, but added more complexity to implement.

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

TODOs:

  • squashed commits
  • includes documentation
  • adds unit tests

Release note:

NONE

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. kind/flake Categorizes issue or PR as related to a flaky test. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. area/provider/azure Issues or PRs related to azure provider sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. labels Apr 20, 2021
@k8s-ci-robot k8s-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Apr 20, 2021
@jsturtevant jsturtevant mentioned this pull request Apr 20, 2021
5 tasks
@CecileRobertMichon
Copy link
Copy Markdown
Contributor

related to #1315

was hoping 8 minutes would be enough but looks like not...

@jsturtevant
Copy link
Copy Markdown
Contributor Author

was hoping 8 minutes would be enough but looks like not...

In my experience fresh windows image pull can take 12-15 mins. We shouldn't being pull a completely fresh Windows image (nano should already be on the node) but outliers in the pull might be taking while.

@CecileRobertMichon
Copy link
Copy Markdown
Contributor

/lgtm
/approve

🤞

@k8s-ci-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: CecileRobertMichon

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

@k8s-ci-robot k8s-ci-robot added lgtm "Looks good to me", indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Apr 20, 2021
@k8s-ci-robot k8s-ci-robot merged commit 319d9b1 into kubernetes-sigs:master Apr 20, 2021
@k8s-ci-robot k8s-ci-robot added this to the v0.5.0 milestone Apr 20, 2021
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. area/provider/azure Issues or PRs related to azure provider cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/flake Categorizes issue or PR as related to a flaky test. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants