This was caused by bad timing as the while the two repositories @updates and @base were updated.
If we would have follower the E405 rule of ansible-lint we would have avoided this failure.
Repositories are updated multiple time every day so the chance of hitting a similar issue is quite real.
Using a simple retry mecanism can make our build more resilient to networking issues.
See https://devops.stackexchange.com/questions/5829/how-to-solve-e405-remote-package-tasks-should-have-a-retry-in-ansible/5837
This was caused by bad timing as the while the two repositories @updates and @base were updated.
If we would have follower the E405 rule of ansible-lint we would have avoided this failure.
Repositories are updated multiple time every day so the chance of hitting a similar issue is quite real.
Using a simple retry mecanism can make our build more resilient to networking issues.
See https:/ /devops. stackexchange. com/questions/ 5829/how- to-solve- e405-remote- package- tasks-should- have-a- retry-in- ansible/ 5837