Skip to content

Fix missing time unit on kind-bootstrap timeout default - #26

Merged
scotwells merged 1 commit into
mainfrom
fix/kind-bootstrap-timeout-unit
Apr 10, 2026
Merged

Fix missing time unit on kind-bootstrap timeout default#26
scotwells merged 1 commit into
mainfrom
fix/kind-bootstrap-timeout-unit

Conversation

@scotwells

@scotwells scotwells commented Apr 10, 2026

Copy link
Copy Markdown
Contributor

Summary

While setting up an e2e testing environment for unikraft-provider, the kind-bootstrap action failed because kubectl wait --timeout 300 is missing the s duration suffix. Newer kubectl versions require it.

Fixes the wait_timeout input default from 300 to 300s.

The kind-bootstrap action's wait_timeout input defaulted to "300"
(bare number) which newer kubectl rejects as an invalid duration.
Changed to "300s" to match the Taskfile's own default.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@scotwells
scotwells enabled auto-merge April 10, 2026 16:33
@scotwells
scotwells merged commit 9c7ef8a into main Apr 10, 2026
2 checks passed
@scotwells
scotwells deleted the fix/kind-bootstrap-timeout-unit branch April 10, 2026 18:53
scotwells added a commit to datum-cloud/unikraft-provider that referenced this pull request Apr 10, 2026
Picks up the kubectl wait timeout fix from datum-cloud/test-infra#26.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant