metalink error on vagrant+ansible up.sh about gluster-kubernetes HOT 7 CLOSED

Moving the conversation form #58 here:

@obnoxxx, I think you were running into this issue. Could you weigh in on this? I'm not sure this is a bug in the vagrant setup, I think this is some sort of networking/DNS issue.

from gluster-kubernetes.

The fix in #61 does not fully fix it. I'm getting repomd.xml does not match metalink for epel errors on at least one random nodes during the vagrant provision. I can't actually get a successful provision after 4 attempts.

from gluster-kubernetes.

I managed to fix this by adding retry logic to the "install base packages" task. It isn't pretty but I suspect there are some underlying network issues with the VMs it creates. I occasionally get the docker pull tasks to fail too. Or maybe it's just my network.

- name: install base packages
  command: yum -y install {{ install_pkgs }}
  register: task_result
  until: task_result.rc == 0
  retries: 5
  delay: 1

from gluster-kubernetes.

@ravishivt - yeah, I was testing some retry logic as well on Friday but I couldn't get mine to work for some reason. Thinks it's a good idea to have some retry logic in some key spots, I will add this in a PR...thanks!

from gluster-kubernetes.

@screeley44 Sounds great. IMHO, the fixes in #61 should be reverted. It adds complexity but doesn't improve the outcome. In my tests, I had the same behavior when using or not using the additional logic in #61.

from gluster-kubernetes.

@ravishivt - agreed, will also revert those #61 changes

from gluster-kubernetes.

Just chiming in to say I like the more elegant retries solution. @screeley44, just a request to make sure the revert is its own commit. :)

from gluster-kubernetes.