Skip to content
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.

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

Add iPXE autoboot retries: #157

Closed

Conversation

jacobweinstock
Copy link
Member

Description

Sometimes there are issues in iPXE or the network that retries can resolve.

Why is this needed

Fixes: #

How Has This Been Tested?

How are existing users impacted? What migration steps/scripts do we need?

Checklist:

I have:

  • updated the documentation and/or roadmap (if required)
  • added unit or e2e tests
  • provided instructions on how to upgrade

Copy link

codecov bot commented Apr 18, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.82%. Comparing base (fc5ed25) to head (8aa5c20).
Report is 36 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #157   +/-   ##
=======================================
  Coverage   97.82%   97.82%           
=======================================
  Files           5        5           
  Lines         367      367           
=======================================
  Hits          359      359           
  Misses          4        4           
  Partials        4        4           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@jacobweinstock
Copy link
Member Author

Hey @nshalman , if you get some cycles I wanted to get your feedback here. Thanks, much appreciated!

Sometimes there are issues in iPXE or the
network that retries can resolve.

Signed-off-by: Jacob Weinstock <jakobweinstock@gmail.com>
@jacobweinstock
Copy link
Member Author

whoops, duplicate of #87. Closing.

@nshalman
Copy link
Member

whoops, duplicate of #87. Closing.

Does it make sense to document the reason that retry logic is not implemented somewhere so that we don't find ourselves thinking about adding it every N months?

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