Closed dtoubelis closed 8 years ago
Thanks!
FYI @techhat
@dtoubelis This is a regression. I can confirm this issue with a salt-cloud -f list_nodes azure
and can reproduce this stacktrace with 2015.8.1, but just switching back to 2015.8.0 without any other changes works fine.
@dtoubelis Are you in a position to try the HEAD of 2015.8? I can't reproduce the failure there.
Since I haven't heard back here, I am going to close this. This is a regression with 2015.8.1 but is fixed at the HEAD of the 2015.8 branch and will be fixed on the upcoming 2015.8.2 branch. If this issue persists when 2015.8.2 is released, let us know and we'll be happy to reopen. Thanks!
Sounds good. Thanks.
When provisioning node I get this:
Even though the command times out, the node is created in azure and I can ssh into it but it is not provisioned, not even salt-minion is installed so obviously salt-bootstrap did not run. However, if I try list running instances I get this:
I'm painfully aware about limitations that Azure imposes on instance names and all instance names I create are between 3-15 characters long, do not contain dots or other illegal characters and always begin with letter.
Also, trying to delete the instance with
salt-cloud
also fails with a similar error but unfortunately I do not have trace.Oh BTW, I'm using azure SDK 0.11.1 since version 1.0.2 does not work with my version of salt.