Closed maxbenson closed 6 years ago
I am going to have to setup azurearm to test this, so it may take me a bit.
Thanks for reporting Daniel
Ok, I am unable to replicate this.
I did have to use the 2017.7 branch to even get this started, would you be able to test that branch to see if a fix for this has already been merged in?
Thanks, Daniel
Just to be clear, you pulled from https://github.com/saltstack/salt/tree/2017.7 with latest commit 88a776d9d2a4d5c133d03532cef45cadd4514718
, correct?
Any luck trying to replicate after pulling from the tag? https://github.com/saltstack/salt/tree/v2017.7.0
Also, for your working run can you also share your pip freeze
? I just want to make sure everything is identical when I try the 2017.7 branch on a different VM.
I just did a straight pip install azure azure-storage azure-cli
and installed the newest of all three.
Unfortunately I have killed the server that has this on it, but I was running off of that first one yes.
And yeah, i ran into a problem with something not having as_dict
available to it on the 2017.7.0 branch as well.
Ok, I've got it working now.
First off, we've got 2017.7.0 installed from what's on the salt-stack yum repo, which is likely built from what's in the v2017.7.0 tag mentioned above. The as_dict
issue you mentioned exists on that tag, and I was able to get around it by manually applying the fix detailed here. I bet that if you were to manually apply the same fix to an environment running the v2017.7.0 tag, you would then run into my TypeError: 'instancemethod' object does not support item assignment
problem.
At any rate, it does appear that what's on the 2017.7 branch (I passed commit hash 88a776d9d2a4d5c133d03532cef45cadd4514718
to the salt-bootstrap script) does resolve this issue. However, I only discovered this after first trying to resolve it with version 2017.7.2 from the salt-stack yum repo--unfortunately I still ran into the problem with that artifact as well.
My findings have left me a bit confused. How come the 2017.7 branch contains the fix for this issue, but the 2017.7.2 yum release (built 10/10/2017) does not? Was this resolved sometime in the past week? Will the current contents of the 2017.7 branch eventually be tagged as 2017.7.3 and shipped to the yum repo, or will 2017.7.3 be tagged from some other source?
I guess the core of my confusion here is that I'm not sure I understand the difference between what's on develop and what's on the 2017.7 branch.
Thanks for looking into this.
The fix for this was included in the 2017.7 branch after 2017.7.2 was branched off for a release.
https://docs.saltstack.com/en/latest/topics/development/contributing.html#dot-release-branches
We would have released 2017.7.2 about 2 weeks before 10/10/17, but a bug was found and that had to be fixed first before we could release so there were about 4 weeks between branching 2017.7.2 and it being released, during which time patches go into 2017.7 branch.
These fixes will be in 2017.7.3
Description of Issue/Question
I'm trying to provision a VM using a salt-cloud azurearm profile. The NIC is provisioned successfully, but the provisioning job fails when it attempts to get and assign information about the NIC. Looking at the NIC properties in the Azure console, I can see it correctly gets assigned VNet, subnet, VM resource group, and NSG.
Setup
Provider:
Profile:
Steps to Reproduce Issue
In my case I've been using
salt-run cloud.map_run mapdata=...
, but the same behavior happens when I simply executesalt-cloud -p vm_profile test-vm1
. The VM NIC is created successfully, but the VM provisioning fails when trying to get the NIC resource group. Throws the following stacktrace:Versions Report
pip freeze:
The above
pip freeze
is from my latest run (trying outazure==2.0.0rc5
); however, the issue is also reproducible pinning thepip install
toazure==2.0.0rc6
.I've also verified that all modules listed here import successfully with
python -c 'import ...'
.Thanks