Description of problem: Was doing an OCP deploy and eventually had this error: 2016-12-14 15:00:59,409 p=24540 u=foreman | failed: [how-high-ose-master1.b.b] (item=git) => {"changed": true, "cmd": "sudo yum install -y git", "delta": "0:00:12.209071", "end": "2016-12-14 20:00:59.782602", "failed": true, "item": "git", "rc": 1, "start": "2016-12-14 20:00:47.573531", "stderr": "https://b.b.b/pulp/repos/Default_Organization/Library/content/dist/rhel/server/7/7Server/x86_64/os/rsync-3.0.9-17.el7.x86_64.rpm: [Errno 14] HTTPS Error 502 - Bad Gateway\nTrying other mirror.\n\n\nError downloading packages:\n rsync-3.0.9-17.el7.x86_64: [Errno 256] No more mirrors to try.", "stdout": "Loaded plugins: package_upload, product-id, search-disabled-repos, subscription-\n : manager\nResolving Dependencies\n--> Running transaction check\n---> Package git.x86_64 0:1.8.3.1-6.el7_2.1 will be installed\n--> Processing Dependency: perl-Git = 1.8.3.1-6.el7_2.1 for package: git-1.8.3.1-6.el7_2.1.x86_64\n--> Processing Dependency: perl >= 5.008 for package: git-1.8.3.1-6.el7_2.1.x86_64\n--> Processing Dependency: rsync for package: git-1.8.3.1-6.el7_2.1.x86_64\n--> Processing Dependency: perl(warnings) for package: git-1.8.3.1-6.el7_2.1.x86_64\n--> Processing Dependency: perl(vars) for package: git-1.8.3.1-6.el7_2.1.x86_64\n--> Processing Dependency: perl(strict) for package: git-1.8.3.1-6.el7_2.1.x86_64\n--> Processing Dependency: perl(lib) for package: git-1.8.3.1-6.el7_2.1.x86_64\n--> Processing Dependency: perl(Term::ReadKey) for package: git-1.8.3.1-6.el7_2.1.x86_64\n--> Processing Dependency: perl(Git) for package: git-1.8.3.1-6.el7_2.1.x86_64\n--> Processing Dependency: perl(Getopt::Long) for package: git-1.8.3.1-6.el7_2.1.x86_64\n--> Processing Dependency: perl(File::stat) for package: I was able to go to the host above and do the yum install of git and then resume the deployment and it finish. Version-Release number of selected component (if applicable): QCI-1.1-RHEL-7-20161212.t.2 How reproducible: Only seen it once. Steps to Reproduce: 1. Do an OCP deployment. Actual results: I received the above error. Expected results: No errors.
I have run through 3 deployments of OCP and have yet to hit this issue. It appears to be a CDN issue for something related to lazy sync. Please grab all pulp and Apache logs if you hit this error again.
*** This bug has been marked as a duplicate of bug 1410140 ***