Different syntax of the same command showing different result

[ssmsa]

Hello everyone.
I installed a Proxmox VM to test communication with my Ceph cluster. I ran a command in my Proxmox node and I was baffled with this output. I thought '-v' and 'version' of 'ceph' command would be showing the same output. But it didn't.
If anyone would be gracious to describe it to me, It would be nice. By the way my Ceph server has the version 'pacific' installed, and The Proxmox node, which will act as Ceph client, it has the Ceph version 'nautilus' installed.



Here is my server:
proxmox-ve: 6.4-1 (running kernel: 5.4.106-1-pve)
pve-manager: 6.4-14 (running version: 6.4-14/15e2bf61)
pve-kernel-5.4: 6.4-15
pve-kernel-helper: 6.4-15
pve-kernel-5.4.174-2-pve: 5.4.174-2
pve-kernel-5.4.106-1-pve: 5.4.106-1
ceph-fuse: 14.2.22-pve1
corosync: 3.1.5-pve2~bpo10+1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.22-pve2~bpo10+1
libproxmox-acme-perl: 1.1.0
libproxmox-backup-qemu0: 1.1.0-1
libpve-access-control: 6.4-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.4-4
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.2-3
libpve-storage-perl: 6.4-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.1.13-2
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.6-2
pve-cluster: 6.4-1
pve-container: 3.3-6
pve-docs: 6.4-2
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-4
pve-firmware: 3.3-2
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-6
pve-xtermjs: 4.7.0-3
qemu-server: 6.4-2
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.7-pve1

 

[t.lamprecht]

ceph version show's the ceph monitor daemon version, i.e., what's running in the ceph server cluster you talk with, while ceph -v shows the ceph CLI client binaries version, i.e., what your client is build with.

That normally only can happen if you use an external ceph cluster, one that isn't managed in a hyper-converged way at the same PVE cluster. The pveversion output supports that assumption too, as there is no ceph server component package listed and the ceph-fuse client that comes always preinstalled is at a nautilus 14.2 version.

Note, some difference in client to server is not too problematic, ceph server has normally quite OK backwards compatibility to the last few versions of the client, but you may not be able to leverage the newer server version to the fullest.

You can add a ceph repository from a newer ceph release to your Proxmox VE host (see here) and just do a standard.

apt update
apt full-upgrade

FYI: we do not add that repo by default as user upgrading from the previous Proxmox VE release may run an even older ceph server version, that cannot be upgraded directly to pacific.