I'm sorry, It's a bug with the new release that manifests on some systems: https://github.com/openwisp/ansible-openwisp2/issues/68
We are working on it. Federico On Tuesday, January 2, 2018 at 5:57:53 AM UTC+1, William Shi wrote: > > I'm still getting the same error with my old set of vms and a fresh set of > vms. In addition I'm still getting the same error when trying the old fix I > was getting before when trying to do the sudo ./manage.py migrate. The > source env/bin/activate should activate the virtual enviroment yes? I also > have the (Env) tag in front of the commands I'm running so I know the > python virtual enviroment is activated. > > p.s Happy New Years! > > On Friday, December 29, 2017 at 12:40:44 PM UTC-6, Federico Capoano wrote: >> >> It was probably a bug, this release should fix it: >> https://github.com/openwisp/ansible-openwisp2/releases/tag/0.7.2 >> >> Commit is: >> https://github.com/openwisp/ansible-openwisp2/commit/2277660a5f6c851c4c1290f728a2111eaa3d9e9c >> >> F. >> > -- You received this message because you are subscribed to the Google Groups "OpenWISP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
