[ceph-users] Re: Debian package for 18.2.4 broken

2024-08-01 Thread Thomas Lamprecht
Hi,

On 01/08/2024 19:49, Burkhard Linke wrote:
> the Debian bookworm packages for 18.2.4 are completely broken and unusable:
> 
> 1. missing dependencies, e.g. python3-packaging:

This is https://tracker.ceph.com/issues/67290 and I submitted a PR:
https://github.com/ceph/ceph/pull/58956
 
> 2. After installing missing dependencies activating encrypted OSDs fails:
> 
> root@cc-r3-ceph-2:~# ceph-volume lvm activate --all
> --> Activating OSD ID 875 FSID 06296c01-4c59-4fde-afe4-0e1e4f078ba9
> -->  InvalidVersion: Invalid version: 'cryptsetup 2.6.1 flags: UDEV BLKID 
> KEYRING KERNEL_CAPI '

this is a missing backport of:
https://github.com/ceph/ceph/commit/dc28b77a6ea50b3390663ac02eeb80367650b7ed
albeit the respective issue hasa backport request open since two months:
https://tracker.ceph.com/issues/66393
not sure why it was not completed..

Plus a follow-up of the above missing commit:
https://github.com/ceph/ceph/commit/607eb34b2c278566c386efcbf3018629cf08ccfd
https://tracker.ceph.com/issues/66393
That is also pending a backport since two months.

FWIW, a version with those things fixed and actually tested is available on
our "test" ceph reef repo:
https://pve.proxmox.com/wiki/Package_Repositories#_ceph_reef_test_repository

See here for the release key used to sign those packages:
https://pve.proxmox.com/wiki/Package_Repositories#repos_secure_apt

regards
 Thomas
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io


[ceph-users] Re: ref v18.2.0 QE Validation status

2023-08-03 Thread Thomas Lamprecht
Am 03/08/2023 um 00:30 schrieb Yuri Weinstein:
> 1. bookworm distro build support
> We will not build bookworm until Debian bug
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030129 is resolved


FYI, there's also a bug in Debian's GCC 12, which is used by default
in Debian Bookworm, that causes issues with the gf-complete erasure
coding library and older AMD CPU's generating illegal instructions
which then kills e.g. the ceph-mon

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012935

Their workaround is to compile gf-complete explicitly with -O1:

https://salsa.debian.org/openstack-team/third-party/gf-complete/-/commit/7751c075f868bf95873c6739d0d942f2a668c58f

While we (Proxmox) saw it for Ceph Quincy and didn't yet confirm it
for upcoming Ceph Reef, it's quite likely still there as the compiler
here seems to be at fault (and gf-complete code didn't change since
quincy FWICT).

- Thomas
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io


[ceph-users] Re: building ceph Nautilus for Debian Stretch

2020-03-02 Thread Thomas Lamprecht
Hi,

On 3/3/20 8:01 AM, Stefan Priebe - Profihost AG wrote:
> does anybody have a guide to build ceph Nautilus for Debian stretch? I
> wasn't able to find a backported gcc-8 for stretch.

That's because a gcc backport isn't to trivial, it may even require rebuild,
of very basic libraries as libc/libcc which isn't to ideal..[0]

When faced with the issue to build Mimic and later releases on Stretch we
looked quite into the issue[0] and decided against it, but instead rebuild
luminous on buster for a sane upgrade path. One, and some actually did, build
newer releases for stretch but IMO that only navigates you into very
unsupported territory.

Debian Stretch will get EOL this year[1], probably around summer, so why not
already update to Buster and save you some hassle?

[0]: http://lists.ceph.com/pipermail/ceph-users-ceph.com/2018-June/027475.html
[1]: https://wiki.debian.org/DebianReleases#Production_Releases

cheers,
Thomas
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io