-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
set_fact not valid during rebuild #253
Comments
Documentation contains some information (tags that influence the behavior) that I'll test. |
This is correct, you should run with
No worries, thank you for your time opening this!
Hmm, this actually sounds like a bug as bender should not cache |
Hey, when ran on a pristine system it should always hit the when built via
I've tried some combinations of ansible versions, and caching flags but none seem to made any effect on |
ah ok I see it fails on this statement:
get() probably doesn't default to |
@grzegorznowak thanks for digging into it! I will gladly accept a pull request :) (I am fairly busy this week so it may take me a few days to respond but things should be getting better in the coming weeks) |
Hi,
I'm using set_fact in a couple of places, e.g. below to get the 'real' hostname to send collectd data to grafana for the host with its real name.
That works pretty well - until I rerun ansible-bender in which case he ignores the sets and uses a cached image, I assume.
I can rerun ansible-bender with --no-cache and it starts working again, however I'm feeling that I do something wrong, maybe?
Playbook extract
Initial run - works fine
next run - fails
PS: I really like ansible-bender - and I understand its a tough job to run a 1-man project like this. Please consider this as a request for input - not a complaint :-)
Is there a good way around this issue - besides building from scratch every time?
Itsmee
The text was updated successfully, but these errors were encountered: