Closed maxbenson closed 5 years ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.
Description of Issue/Question
Executing any salt-cloud command with azurearm that calls the
list_nodes_full
method will throw an exception if there are any nodes in any resource group that do not have a NIC associated with them.Setup
I'm running on a very recent commit installed with salt-bootstrap:
sh bootstrap-salt.sh -M -L -X git e1853e5b5b8109d3b4aebbd22a48b75e92bbb554
. I did a quick check ofazurearm.py
on the2017.7
branch and it looks like this will encounter the same problem there.Steps to Reproduce Issue
I originally found this by attempting to destroy a VM with
salt-cloud -d <name>
; however, it appears to happen with any salt-cloud command that winds up calling thelist_nodes_full
method. I have a stopped VM in another resource group with no NIC, and this VM isn't related to my salt-cloud command at all. The following stacktrace is the result of runningsalt-cloud --action show_instance <name> -l debug
.I feel like it should be the responsibility of salt-cloud to sanitize that potential empty result and catch the
CloudError
raised bynetwork_interfaces_operations.py:177
.Versions Report
pip freeze: