Infrastructure » sepia

Resolved by https://github.com/ceph/ceph-cm-ansible/pull/117

I am still seeing this error during upgrades:

2015-09-23T13:15:13.742 INFO:teuthology.orchestra.run.vpm042.stderr:
2015-09-23T13:15:13.742 INFO:teuthology.orchestra.run.vpm042.stderr: One of the configured repositories failed (Unknown),
2015-09-23T13:15:13.742 INFO:teuthology.orchestra.run.vpm042.stderr: and yum doesn't have enough cached data to continue. At this point the only
2015-09-23T13:15:13.743 INFO:teuthology.orchestra.run.vpm042.stderr: safe thing yum can do is fail. There are a few ways to work "fix" this:
2015-09-23T13:15:13.743 INFO:teuthology.orchestra.run.vpm042.stderr:
2015-09-23T13:15:13.743 INFO:teuthology.orchestra.run.vpm042.stderr:     1. Contact the upstream for the repository and get them to fix the problem.
2015-09-23T13:15:13.743 INFO:teuthology.orchestra.run.vpm042.stderr:
2015-09-23T13:15:13.744 INFO:teuthology.orchestra.run.vpm042.stderr:     2. Reconfigure the baseurl/etc. for the repository, to point to a working
2015-09-23T13:15:13.744 INFO:teuthology.orchestra.run.vpm042.stderr:        upstream. This is most often useful if you are using a newer
2015-09-23T13:15:13.744 INFO:teuthology.orchestra.run.vpm042.stderr:        distribution release than is supported by the repository (and the
2015-09-23T13:15:13.744 INFO:teuthology.orchestra.run.vpm042.stderr:        packages for the previous distribution release still work).
2015-09-23T13:15:13.745 INFO:teuthology.orchestra.run.vpm042.stderr:
2015-09-23T13:15:13.745 INFO:teuthology.orchestra.run.vpm042.stderr:     3. Disable the repository, so yum won't use it by default. Yum will then
2015-09-23T13:15:13.745 INFO:teuthology.orchestra.run.vpm042.stderr:        just ignore the repository until you permanently enable it again or use
2015-09-23T13:15:13.745 INFO:teuthology.orchestra.run.vpm042.stderr:        --enablerepo for temporary usage:
2015-09-23T13:15:13.746 INFO:teuthology.orchestra.run.vpm042.stderr:
2015-09-23T13:15:13.746 INFO:teuthology.orchestra.run.vpm042.stderr:            yum-config-manager --disable <repoid>
2015-09-23T13:15:13.746 INFO:teuthology.orchestra.run.vpm042.stderr:
2015-09-23T13:15:13.746 INFO:teuthology.orchestra.run.vpm042.stderr:     4. Configure the failing repository to be skipped, if it is unavailable.
2015-09-23T13:15:13.747 INFO:teuthology.orchestra.run.vpm042.stderr:        Note that yum will try to contact the repo. when it runs most commands,
2015-09-23T13:15:13.747 INFO:teuthology.orchestra.run.vpm042.stderr:        so will have to try and fail each time (and thus. yum will be be much
2015-09-23T13:15:13.747 INFO:teuthology.orchestra.run.vpm042.stderr:        slower). If it is a very temporary problem though, this is often a nice
2015-09-23T13:15:13.747 INFO:teuthology.orchestra.run.vpm042.stderr:        compromise:
2015-09-23T13:15:13.748 INFO:teuthology.orchestra.run.vpm042.stderr:
2015-09-23T13:15:13.748 INFO:teuthology.orchestra.run.vpm042.stderr:            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
2015-09-23T13:15:13.748 INFO:teuthology.orchestra.run.vpm042.stderr:
2015-09-23T13:15:13.748 INFO:teuthology.orchestra.run.vpm042.stderr:Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again

PR 142 on ceph-cm-ansible should fix this.

If it doesn't, I'm thinking we need to make sure ca-certificates package is up to date earlier in the testnodes playbook.

I haven't heard any more complaints about this bug so marking it resolved.