we now have to handle the version of 'old' nodes, as well as the
new nodes, which are missing the 'version' field in the metadata/osd call
so set the 'versions' object to a default empty object for osds
and get the host version directly from the treenode
(the parent node of the osd node)
also compare the host version in the dashboard by getting first the
new version field, and the old one as fallback.
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
It seems we did not prepare the GUI enough for the API changes
planned when stopping to broadcast the old single string version. We
have to use the node specific versions, not the global 'versions'
object.
Also use the `PVE.Utils.compare_ceph_versions` everywhere, since some
versions are strings and others are the parts of the version (e.g.
["16", "2, "6"])
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
show the difference between a service where the host has outdated
packages, and where only the service runs an outdated version and only
needs to restart
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
to have 2 different states for
* packages are outdated
* packages are up to date but the service runs with the old version
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
sometimes a monitor id is only mentioned in a later part of the message
not always the first
for example, if more than one monitor is missing the msgr2 protocol
each monitor gets its own line
before this patch the whole error would only be attributed to the first
monitor mentioned, now it is attributed to all
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
Used for a new Panel in ceph dashboard, shows the ceph services
managed by us (mon,mgr,mds)
some code is copied from 'ceph/StatusDetail.js' and is not necessary there
anymore
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
