fix: device needs to be ready on node publish

[lukasmetzner]

No description provided.

[codecov]

Codecov Report

❌ Patch coverage is 85.18519% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 72.17%. Comparing base (29289b1) to head (d7586bf).

Files with missing lines	Patch %	Lines
internal/volumes/mount.go	85.18%	3 Missing and 1 partial ⚠️

Additional details and impacted files

@@                        Coverage Diff                        @@
##           refactor-loop-through-context    #1381      +/-   ##
=================================================================
+ Coverage                          71.97%   72.17%   +0.19%     
=================================================================
  Files                                 17       17              
  Lines                               1495     1520      +25     
=================================================================
+ Hits                                1076     1097      +21     
- Misses                               333      336       +3     
- Partials                              86       87       +1     

Flag	Coverage Δ
e2e-controller	56.90% <85.18%> (+0.45%)	⬆️
e2e-node	56.90% <85.18%> (+0.45%)	⬆️
integration	3.19% <0.00%> (-0.08%)	⬇️
unit	40.85% <0.00%> (-0.69%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[jooola]

With a 500ms cap, we might as well just wait 500ms every time. What is the reason for having such a small cap? Could we increase the cap to e.g. 5s?

(Without cap, we would have a total waiting time of 12.8 seconds, with a max of 7 retries)

[lukasmetzner]

We don't fully understand yet why this device appears late. Talking with internal teams, one idea is that the OS is under heavy pressure. This seems to happen very rarely, as we don't have a lot of issue reports from customers.

My idea was to quickly retry in small intervals, to absorb the delays caused by the OS being busy.