Package: glusterfs-client Version: 10.3-5 Severity: normal Dear Maintainer,
I have a bullseye GlusterFS cluster which uses SSL/TLS. Three machines have a replica of the data, and an additional one merely mounts the cluster without local storage for purposes of backing it up. I recently upgraded the backup machine to bookworm. Suddenly I was unable to mount the cluster. The key error in the logs was: E [socket.c:4405:ssl_setup_connection_params] 0-glusterfs: could not load our cert at /usr/lib/ssl/glusterfs.pem /usr/lib/ssl/ is a strange path. As far as I can tell, the correct path is /etc/ssl/. Creating three symlinks fixed the problem and allowed the cluster to be mounted: /usr/lib/ssl/glusterfs.ca -> /etc/ssl/glusterfs.ca /usr/lib/ssl/glusterfs.pem -> /etc/ssl/glusterfs.pem /usr/lib/ssl/glusterfs.key -> /etc/ssl/glusterfs.key Taking another look at the apt-listchanges output for the upgrade, there is nothing from any gluster package. This leads me to believe that the changing of this path was unintentional and is a bug. Not sure what's the best thing to do about it at this point, since fixing it would break people's existing bookworm configurations. -- System Information: Debian Release: 12.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-13-amd64 (SMP w/24 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages glusterfs-client depends on: ii glusterfs-common 10.3-5 ii libc6 2.36-9+deb12u3 ii python3 3.11.2-1+b1 glusterfs-client recommends no packages. glusterfs-client suggests no packages. -- no debconf information
