No module named 'flask'

[pradeepb6]

Hi,
Could you please look at this issue? Thanks

[aoxborrow]

Hi Pradeep, did the Ansibile provisioning complete without errors? It should have installed Flask for you from requirements.txt. Can you try running this command from within the VM/Vagrant and see what version Ansible you have?
ansible --version

I think the provision script is pulling down Ansible 2.0 now and that has broken the scripts. I am going to update it for Ansible 2.0 shortly.

[pradeepb6]

Hi,
Ansible version is

ansible 2.0.1.0
config file =
configured module search path = Default w/o overrides

And I got error while doing ansible provisioning, not sure whether its major issue.

==> default: TASK [common : Use our custom .profile for bash] *******************************
==> default: fatal: [localhost]: FAILED! => {"changed": true, "failed": true, "msg": "Destination /home not writable"}
==> default:
==> default: NO MORE HOSTS LEFT *************************************************************
==> default: to retry, use: --limit @/home/vagrant/fvang/ansible/dev.retry
==> default:
==> default: PLAY RECAP *********************************************************************
==> default: localhost : ok=3 changed=2 unreachable=0 failed=1
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

[aoxborrow]

Yes, that is a fatal error that caused the provisioning to stop early. So it didn't get to the other tasks like setting up your virtualenv and python libraries. I will update the scripts for Ansible 2.0, shouldn't take long.

[pradeepb6]

thanks a lot for the swift response :)

[aoxborrow]

I just updated it to work with Ansible 2.0 and simplified a few things. Everything should work as expected now, give it a shot. You'll probably want to just vagrant destroy and vagrant up again.

Also, mark accepted answer on StackOverflow? :)

[pradeepb6]

Sure. Thank you very much. Right now I am running the setup. Will get back to you if everything works fine :)

On Mon, Mar 21, 2016 at 11:21 PM, Aaron Oxborrow < notifications@github.com [notifications@github.com] > wrote:
I just updated it to work with Ansible 2.0 and simplified a few things. Everything should work as expected now, give it a shot. You'll probably want to just vagrant destroy and vagrant up again.

Also, mark accepted answer on StackOverflow? :)

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub [https://github.com//issues/2#issuecomment-199514339]