Bug #13794
closedFeature #13622: Change the task to `yum install -x librbd-devel -x librados-devel ceph`
librados2 packaging and firefly testing.
0%
Description
While teuthology was doing installs for bug 13622, the installation of the following packages fail due to conflicts with librados2 and librbd1: ceph-radosgw ceph-test ceph-devel ceph ceph-fuse python-ceph and rbd-fuse. A workaround for this problem is that we removed librados2 and librbd1 before doing these installs.
This workaround broke qemu-kvm since the librados2 removal also remove qemu-kvm since that was depended on it.
So the workaround is not good. If this installation problem can be solved by packaging changes, we don't need to remove these libraries and all would be well.
So I am filing this ticket in the hopes that it can be fixed by packaging things nicely.
If not, we may be able to fix things by reinstalling qemu-kvm after we do the ceph installs. But even to me, that solution looks pretty goofy.
Updated by Yuri Weinstein over 8 years ago
- Release set to firefly
- ceph-qa-suite rbd added
Here is the run to illustrate the issue:
http://pulpito.ceph.com/teuthology-2015-11-12_17:03:29-rbd-firefly-distro-basic-vps/
Job one: 1147816
2015-11-12T17:20:32.966 INFO:teuthology.orchestra.run.vpm120:Running: 'sudo yum install ceph-debuginfo -y -x librbd1-devel -x librados2-devel'
2015-11-12T17:20:32.929 INFO:teuthology.orchestra.run.vpm120.stdout: librados2.x86_64 1:0.80.7-2.el7 2015-11-12T17:20:32.929 INFO:teuthology.orchestra.run.vpm120.stdout: 2015-11-12T17:20:32.929 INFO:teuthology.orchestra.run.vpm120.stdout:Dependency Removed: 2015-11-12T17:20:32.929 INFO:teuthology.orchestra.run.vpm120.stdout: librbd1.x86_64 1:0.80.7-2.el7 2015-11-12T17:20:32.929 INFO:teuthology.orchestra.run.vpm120.stdout: qemu-img.x86_64 10:1.5.3-86.el7_1.8 2015-11-12T17:20:32.929 INFO:teuthology.orchestra.run.vpm120.stdout: qemu-kvm.x86_64 10:1.5.3-86.el7_1.8 2015-11-12T17:20:32.929 INFO:teuthology.orchestra.run.vpm120.stdout: qemu-kvm-common.x86_64 10:1.5.3-86.el7_1.8
Updated by Josh Durgin over 8 years ago
If this can't be fixed in packaging, can we get around this by having teuthology use a yum transaction to replace the old librbd and librados atomically, without uninstalling anything else?
iirc that worked for me in the past.
Updated by Ken Dreyer over 8 years ago
Boris, if we bumped the Epoch in the firefly branch upstream, that would fix this issue, right?
Updated by Boris Ranto over 8 years ago
Mostly. It would still break if you tried to install an earlier firefly version or any dumpling version.
Updated by Boris Ranto over 8 years ago
@Josh Jones: The QE could run 'yum downgrade librados2 librbd1' as a workaround instead of yum remove. That might work as well.
Updated by Ken Dreyer over 8 years ago
Boris Ranto wrote:
Mostly. It would still break if you tried to install an earlier firefly version or any dumpling version.
That's acceptable. dumpling is EOL, and I don't know of tests that install old firefly versions of librbd1/librados2.
Updated by Anonymous over 8 years ago
I tried it with the download instead of remove
The ceph-radosgw test works:
http://pulpito.ceph.com/ubuntu-2015-11-16_10:43:18-rgw-firefly-distro-basic-vps/
The qemu test fails:
http://pulpito.ceph.com/ubuntu-2015-11-16_10:28:56-rbd-firefly-distro-basic-vps/
One thing to note is that the qemu test succeeds as far as the installation is concerned but fails shortly thereafter. It is not clear to me right now if this failure is an installation problem or an unrelated issue
Updated by Boris Ranto over 8 years ago
The log suggests that the failed command is the one trying to remove an rbd image. This is done in the generator function create_image in tasks/rbd.py of ceph-qa-suite which also creates the image.
I don't see how this would be related to an installation issue -- afaik, that should succeed even if qemu was not installed.
Updated by Ken Dreyer over 8 years ago
- Status changed from New to 7
https://github.com/ceph/ceph/tree/wip-11104-firefly-add-epoch bumps the Firefly packages' Epoch to "1".
Updated by Boris Ranto about 8 years ago
I think we can close this one, it does not seem to bite us any more.
@Ken|Yuri|Warren: Any objections?
Updated by Yuri Weinstein about 8 years ago
Yes can close and we firefly is EOL
Updated by Anonymous almost 8 years ago
- Status changed from Need More Info to Closed
This bug and 13622 should no longer be affecting things.