-
-
Notifications
You must be signed in to change notification settings - Fork 146
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
Fix #23 #25
Fix #23 #25
Conversation
This phenomenon appears to be caused by the environment. As long as I see the log, I think that it would be incorrect to become an failed. Write the log executed with
Playbook log.
|
I also have this issue after upgrading to Ansible 2.5 when using this role to install epel and receive a similar message to: "epel-release-7-11.noarch providing /tmp/epel-release-latest-7.noarch7qzIVW.rpm is already installed" I'm using Vagrant to build VMs with geerlingguy/centos7 as the box/base. If I re-rerun provisioning, everything is ok on the second attempt. |
Seeing this as well with Ansible 2.5.0, however downgrading to 2.4.4 caused it to work again. |
D'oh! Thanks for the PR, checking it over and will merge in a few. |
The role appeared to fail in a non-idempotent way due to task
"failed": true
being set, even whenyum
package was already installed and it should just continue.Looks like checking return code
!= 0
is better in this case, as it's correctly set to0
whenyum
says it's already installed.Error was: