CFE-4628: Fixed a driver-assertion in get_by_name/get_by_uuid when attempting destroy --all whilst they are already destroyed in the cloud

[SimonThalvorsen]

No description provided.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 49.47%. Comparing base (c3b41ce) to head (ca8d758).

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #204      +/-   ##
==========================================
+ Coverage   49.09%   49.47%   +0.37%     
==========================================
  Files          18       18              
  Lines        3214     3214              
==========================================
+ Hits         1578     1590      +12     
+ Misses       1636     1624      -12     

Files with missing lines	Coverage Δ
cf_remote/spawn.py	39.28% <100.00%> (+2.38%)	⬆️

🚀 New features to boost your workflow:

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

[olehermanse]

Needs manual testing

[SimonThalvorsen]

Unable to reproduce the error, assumption is that when Lars tested it that there were no instances running and the list_drivers-method returned an empty list -> evaluated to True and the assert driver-check triggered. This should only happen if no argument is passed, in the case of empty nodelist then it should just iterate over nothing since there are no nodes to match. driver.list_nodes should only run if the node-list is not supplied, not if it is empty.