Hey there, The exact upgrade path that I found worked was (and this is on a CentOS 7 box, but might be v similar for an Ubuntu)
cd ~awx/venv/ansible . bin/activate pip install --upgrade --force-reinstall ansible[azure] First, I activate the virtualenv that Ansible Tower uses when it fires jobs, as I understand it. This is specific for Ansible Tower, so you might need to adjust where you activate your virtualenv from if you're just running Ansible from the command line (or even create one, which I've decided is probably a good idea for overall system stability, rather than installing a bunch of packages directly into the systems' python library) Then I run pip with both the --upgrade and --force-reinstall flags on the ansible[azure] package. Now this worked fine on one dev box that I share with some colleagues, but a different box had some missing core system packages (gcc, libffi-dev, python-dev if I recall) which needed installing. Not sure if that was an edge case or not, it wasn't a very clean system build so might be a bit of a mess. After that, jobs using Azure modules continued to work fine including the newer ones, e.g. azure_rm_virtualmachine_facts As mentioned in an earlier post, I did also have a mistake in my playbook where I was trying to run the azure modules from a target server instead of the ansible server - I wanted to build a fact dictionary that contained the vmSize of various VM's, and the task ran against my inventory without me adding 'delegate_to: localhost' on the task. That caused me to think I still had pip / python issues for a few minutes until I realised what was happening! On Thursday, October 11, 2018 at 8:28:23 AM UTC+1, [email protected] wrote: > > Hi! > > Can you elaborate a bit more what you did exactly to fix this? I'm running > into exactly the same problems with pretty much all ansible[azure] modules. > > Thanks! > > Am Mittwoch, 10. Oktober 2018 13:00:33 UTC+2 schrieb Andy Eff: >> >> Ok disregard previous post, I had in fact forgotten to assign a >> delegate_to: localhost option as I needed to talk to the Azure API from the >> Ansible Tower server and not the remote VM. >> >> I've also confirmed now that everything else I had issues with appears to >> work fine after switching to the Ansible (not awx) virtualenv and doing a >> full 'pip install --upgrade --force-reinstall ansible[azure]' >> So now happily working with Ansible 2.7 + Tower 3.3.0 with Azure modules. >> Hurray! >> >> On Wednesday, October 10, 2018 at 11:55:38 AM UTC+1, Andy Eff wrote: >>> >>> Bit more investigation, looks like this might be an issue with a >>> specific module, so I'll gather some notes and go raise an issue on Github. >>> >>> -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/d7671b1d-fc84-4d4d-b37f-fbd54abbb960%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
