Figured I would chime in as also having this issue. Moving from 16.04 to 18.04 on some OSD nodes. I have been using the ceph apt repo > deb https://download.ceph.com/debian-luminous/ xenial main
During the release-upgrade, it can’t find a candidate package, and actually removes the ceph-osd package. This is what dpkg showed after the reboot: > $ dpkg -l | grep ceph > rc ceph-base 12.2.10-1xenial > amd64 common ceph daemon libraries and management tools > rc ceph-common 12.2.10-1xenial > amd64 common utilities to mount and interact with a ceph > storage cluster > ii ceph-deploy 2.0.1 > all Ceph-deploy is an easy to use configuration tool > ii ceph-fuse 12.2.10-1xenial > amd64 FUSE-based client for the Ceph distributed file system > rc ceph-mds 12.2.10-1xenial > amd64 metadata server for the ceph distributed file system > rc ceph-mgr 12.2.10-1xenial > amd64 manager for the ceph distributed storage system > rc ceph-mon 12.2.10-1xenial > amd64 monitor server for the ceph storage system > rc ceph-osd 12.2.10-1xenial > amd64 OSD server for the ceph storage system > ii libcephfs2 12.2.10-1xenial > amd64 Ceph distributed file system client library > ii python-cephfs 12.2.10-1xenial > amd64 Python 2 libraries for the Ceph libcephfs library After the reboot to complete the upgrade, I tried to install the ceph-osd package back, using the bionic repo, and get complaints about ceph-common and ceph-base, which was an endless rabbit hole of dependencies that lead to libcurl3. My solution in the end to get things back up and running was to remove the ceph repo and move to the Ubuntu repo, and manually specify the package in apt for every package in the chain. > $ sudo apt install ceph-common=12.2.7-0ubuntu0.18.04.1 > ceph-base=12.2.7-0ubuntu0.18.04.1 ceph-fuse=12.2.7-0ubuntu0.18.04.1 > ceph-osd=12.2.7-0ubuntu0.18.04.1 libcephfs2=12.2.7-0ubuntu0.18.04.1 > python-cephfs=12.2.7-0ubuntu0.18.04.1 python-rados=12.2.7-0ubuntu0.18.04.1 > librbd1=12.2.7-0ubuntu0.18.04.1 python-rbd=12.2.7-0ubuntu0.18.04.1 > librados2=12.2.7-0ubuntu0.18.04.1 librados-dev=12.2.7-0ubuntu0.18.04.1 > libradosstriper1=12.2.7-0ubuntu0.18.04.1 Obviously not ideal, but I assume that it will hold me over until the luminous-bionic repos are able to handle libcurl4 dependencies, or my Mimic window rolls around. Just wanted to chime in that I ran into this issue, and how I worked around it. Reed > On Nov 26, 2018, at 11:11 AM, Ken Dreyer <kdre...@redhat.com> wrote: > > On Thu, Nov 22, 2018 at 11:47 AM Matthew Vernon <m...@sanger.ac.uk> wrote: >> >> On 22/11/2018 13:40, Paul Emmerich wrote: >>> We've encountered the same problem on Debian Buster >> >> It looks to me like this could be fixed simply by building the Bionic >> packages in a Bionic chroot (ditto Buster); maybe that could be done in >> future? Given I think the packaging process is being reviewed anyway at >> the moment (hopefully 12.2.10 will be along at some point...) > > That's how we're building it currently. We build ceph in pbuilder > chroots that correspond to each distro. > > On master, debian/control has Build-Depends: libcurl4-openssl-dev so > I'm not sure why we'd end up with a dependency on libcurl3. > > Would you please give me a minimal set of `apt-get` reproduction steps > on Bionic for this issue? Then we can get it into tracker.ceph.com. > > - Ken > _______________________________________________ > ceph-users mailing list > ceph-users@lists.ceph.com > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
