Problem: Vm execution failed due to network interface

[olethanh]

occasionaly vm creation vm because the assigned tap network inteface was already existing. Probably not properly teared down from a previous execution or from a concurrency issue

Displayed Error was :
OSError: [Errno 16] Device or resource busy

it was then looped as a retry and blocked the whole thing

Solution:
When assigning a vm_id, check that the network interface for that vm doesn't already exists This act as a double check for a variety of issues

[github-actions]

Failed to retrieve llama text: POST 504:

504 Gateway Time-out

The server didn't respond in time.

[codecov]

Codecov Report

Attention: Patch coverage is 25.00000% with 6 lines in your changes missing coverage. Please review.

Project coverage is 43.80%. Comparing base (0f77070) to head (4b173d6).
Report is 82 commits behind head on main.

Files	Patch %	Lines
src/aleph/vm/network/hostnetwork.py	40.00%	3 Missing ⚠️
src/aleph/vm/pool.py	0.00%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #596      +/-   ##
==========================================
- Coverage   43.83%   43.80%   -0.04%     
==========================================
  Files          55       55              
  Lines        4944     4952       +8     
  Branches      585      587       +2     
==========================================
+ Hits         2167     2169       +2     
- Misses       2658     2664       +6     
  Partials      119      119              

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

[hoh]

Can we easily get this code tested ?

[olethanh]

Not really automatically as it is at low level but if you want to test it manually you can create a network interface, prior to launching using

sudo ip tuntap add mode tap vmtap4