Skip to content

Reboot retry timeout fix#384

Closed
shivakunv wants to merge 2 commits intomainfrom
reboottimeoutcheck
Closed

Reboot retry timeout fix#384
shivakunv wants to merge 2 commits intomainfrom
reboottimeoutcheck

Conversation

@shivakunv
Copy link
Contributor

No description provided.

@coveralls
Copy link

coveralls commented Jun 2, 2025

Pull Request Test Coverage Report for Build 15386595059

Details

  • 3 of 5 (60.0%) changed or added relevant lines in 2 files are covered.
  • 11 unchanged lines in 1 file lost coverage.
  • Overall coverage decreased (-0.02%) to 14.963%

Changes Missing Coverage Covered Lines Changed/Added Lines %
pkg/provisioner/provisioner.go 0 2 0.0%
Files with Coverage Reduction New Missed Lines %
pkg/provisioner/dependency.go 11 40.2%
Totals Coverage Status
Change from base Build 15363939553: -0.02%
Covered Lines: 262
Relevant Lines: 1751

💛 - Coveralls

@shivakunv shivakunv force-pushed the reboottimeoutcheck branch 2 times, most recently from f2a7146 to 29345c2 Compare June 2, 2025 07:27
interval := 60 * time.Second
retryInterval := 30 * time.Second

time.Sleep(interval)
Copy link
Collaborator

Choose a reason for hiding this comment

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

this is outside of the foor loop, why?

Comment on lines 96 to 97
maxRetries := 9
interval := 60 * time.Second
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why like this?


# Wait for cluster to be ready
with_retry 10 30s kubectl --kubeconfig $KUBECONFIG wait --for=condition=ready --timeout=300s nodes --all
with_retry 5 300s kubectl --kubeconfig $KUBECONFIG wait --for=condition=ready --timeout=300s nodes --all
Copy link
Collaborator

@ArangoGutierrez ArangoGutierrez Jun 2, 2025

Choose a reason for hiding this comment

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

I prefer more retries with a smaller time window, waiting 300s makes it too slow, every 30s is ok. the command is also calling kubectl to wait 300s so 10 x 30s + 300s is enough time already

@shivakunv shivakunv force-pushed the reboottimeoutcheck branch 3 times, most recently from 4cfdb3c to dff8333 Compare June 2, 2025 11:19
shivakunv added 2 commits June 3, 2025 18:51
Signed-off-by: shiva kumar <shivaku@nvidia.com>
Signed-off-by: shiva kumar <shivaku@nvidia.com>
@shivakunv shivakunv force-pushed the reboottimeoutcheck branch from dff8333 to afae7c5 Compare June 3, 2025 13:21
@ArangoGutierrez
Copy link
Collaborator

I we are safe to close this PR

@shivakunv
Copy link
Contributor Author

Thanks @ArangoGutierrez closing

@shivakunv shivakunv closed this Aug 14, 2025
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.

3 participants