Bug #10926
closed
No package ceph-devel-0.92 available.
Added by Sage Weil about 9 years ago.
Updated about 9 years ago.
Description
2015-02-21T18:39:36.798 INFO:teuthology.orchestra.run.plana64:Running: 'sudo yum install ceph-devel-0.92 -y'
2015-02-21T18:39:37.159 INFO:teuthology.orchestra.run.plana64.stdout:Loaded plugins: priorities, product-id, subscription-manager
2015-02-21T18:39:37.205 INFO:teuthology.orchestra.run.plana64.stdout:This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
2015-02-21T18:39:41.526 INFO:teuthology.orchestra.run.plana64.stdout:22 packages excluded due to repository priority protections
2015-02-21T18:39:42.295 INFO:teuthology.orchestra.run.plana64.stdout:No package ceph-devel-0.92 available.
2015-02-21T18:39:43.200 INFO:teuthology.orchestra.run.plana64.stderr:Error: Nothing to do
ubuntu@teuthology:/var/lib/teuthworker/archive/sage-2015-02-21_12:47:21-rados-hammer-distro-basic-multi/773192
tons of these
- Assignee set to Sandon Van Ness
Not sure how this is handled since so many packages are obsoleting it if via yum you are telling it to install the obseleted package (via yum calculating stuff on dependencies) I can play around with this manually a bit to see what our options are to but its not gitbuilder or infrastructure related.
Talking to Ken it looks like the obsoletes should handle this. I will definitely do some manual testing as we want this fixed ASAP.
From playing around manually with this, "yum install ceph-devel-0.92" fails, whereas "yum install ceph-devel" succeeds.
Ok so appending the version is what is causing the problem. I think we were doing that to insure it was getting the right version from the right repo? Didn't we recently make some changes to the priorities so versions in epel and stuff would not get considered? Maybe we don't actually need to be doing that anymore?
If it's done to override EPEL, I wonder if that technique of appending the version number was done long before we started using yum's priorities plugin, because the yum priorities plugin should allow you to basically ignore what's going on downstream in favor of what is in gitbuilder (or ceph.com, or whatever).
Another hunch I had was that the version number might be present here to permit Teuthology to test upgrades from one version of Ceph to another? Is that the case? (total newbie-to-teuthology question :)
I actually don't think we need the version appended anymore. I think the change to the priorities config file to check_obsletes was probably the correct fix and we were getting around it specifying the version number. Testing how teuthology changes the ceph.repo file and manually testing with older versions (even dumpling) without appending versions with the /etc/yum.pluginconf.d/priorities.conf it now appears to be getting the correct version from the repo we specified and before we were probably doing a hack so I think we can safely remove that appended version now. I will make a wip branch and have yuri do a run.
Sounds good. Thanks for looking into this!
Sandon, I can take the teuthology work on this if you'd like. Thanks for looking into this!
- Status changed from New to Fix Under Review
- Assignee changed from Sandon Van Ness to Andrew Schoen
- Status changed from Fix Under Review to Resolved
Also available in: Atom
PDF