ceph_client: on ubuntu 16.04 default Ceph version (hammer) causes conflicts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Expired
|
Undecided
|
Unassigned |
Bug Description
As the summary states osa-ceph_client adds the /etc/apt/
Putting "ceph_stable_
So, modifying the Ceph default to something less archaic (sorry for the hyperbole) would likely solve this. (Especially that Hammer is nearing EOL: https:/
edit: oh, I forgot to add, this is using stable/newton
description: | updated |
Changed in openstack-ansible: | |
status: | New → Incomplete |
Hi, I was doing some debugging on Xenial tonight and I'm having a hard time replicating this. I took a clean Xenial install, added the hammer apt key, repo, and Redhat pin, then installed the packages from the ceph_client role: ceph ceph-common python-ceph.
I wonder if one of our other roles is pulling in ceph packages prior to the ceph_client role running, which would cause this conflict since the unpinned packages from UCA/xenial main would be installed already.
Could you post some debugging from apt-cache, apt-get install, dpkg -l, etc showing the broken setup when you hit the conflicts? An ansible run log would be handy too so we can make sure the apt cache is being refreshed after the repo & pins are added, etc. I was not able to find where we would be pulling in librados from in our other roles, and if it is being installed in ceph_client, we should have everything pinned to hammer before we do any installs.