I've just checked the rax.py file that we're using for our inventory, and I can't find any reference to any caching. If you have a minute Liam, would you mind pasting a working example of how you're using meta: refresh_inventory? It'll most likely turn out to be something that I have done incorrectly.
Thanks! Dan. On 26 February 2016 at 15:09, Dan Rough <[email protected]> wrote: > Hi Liam, > > Thanks for responding - I'd all but given up on getting this to work. > > I'm using Rackspace rather than AWS, I'll see if the Rackspace equivalent, > rax.py has a similar issue with the cache. > > Thanks again! > > Dan. > > On 26 February 2016 at 07:55, Liam Jones <[email protected]> wrote: > >> Hey Dan, >> >> I put what I found in some comments on this stackoverflow >> <http://stackoverflow.com/questions/29003420/reload-ansibles-dynamic-inventory> >> article, >> but have you tried disabling the cache on the dynamic inventory? To >> disable, set cache_max_age = 0 in the ec2.ini file. >> >> This was the issue for me, so maybe it'll help you. >> >> Cheers, >> Liam >> >> On Sunday, 7 February 2016 04:54:02 UTC+8, Dan Rough wrote: >>> >>> Rather than post a new thread, I thought that I would resurrect this >>> one, as Brian's suggestion - to use `meta: refresh_inventory` sounds to be >>> exactly what I'm looking for. However, after some number of attempts, I can >>> not seem to get it to work. Does anyone have an example that they wouldn't >>> mind posting? >>> >>> On Tuesday, 3 November 2015 18:13:51 UTC, Kincaid Savoie wrote: >>>> >>>> We're using 1.9.4, so I had to use set_fact, but it worked like a >>>> charm! Thanks! >>>> >>>> On Monday, November 2, 2015 at 4:56:19 PM UTC-7, Brian Coca wrote: >>>>> >>>>> So in 2.0 you can force ansible to re-execute the inventory script >>>>> with `meta: refresh_inventory`, but if you are using cache or older >>>>> versions try: >>>>> >>>>> set_fact: ansible_ssh_host=127.0.0.1 >>>>> >>>>> >>>>> >>>>> -- >>>>> Brian Coca >>>>> >>>> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Ansible Project" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/ansible-project/Pi6cXCqG0Fw/unsubscribe >> . >> To unsubscribe from this group and all its topics, 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/23f453bf-ced0-4446-ab56-da35d1c80250%40googlegroups.com >> <https://groups.google.com/d/msgid/ansible-project/23f453bf-ced0-4446-ab56-da35d1c80250%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Dan Rough, Chief Operating Officer > t: +44 20 7253 2380 | m: +44 79 8073 9436 | linkedin > <https://uk.linkedin.com/in/danrough> | @danrough > <https://twitter.com/danrough> > Gamevy Limited, 3rd Floor, 87-88 Turnmill Street, London, EC1M 5QU > -- Dan Rough, Chief Operating Officer t: +44 20 7253 2380 | m: +44 79 8073 9436 | linkedin <https://uk.linkedin.com/in/danrough> | @danrough <https://twitter.com/danrough> Gamevy Limited, 3rd Floor, 87-88 Turnmill Street, London, EC1M 5QU -- 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/CAPa%2BBKQbbwP08NKQ5_WQSM0O0xaGTiLpZUvnThGSfyL5sq%2BKsw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
