From: "Naumann, Thomas" <thomas.naumann@ovgu.de>
To: "pve-user@lists.proxmox.com" <pve-user@lists.proxmox.com>
Subject: [PVE-User] Snapshots not visible via Webgui
Date: Mon, 23 Nov 2020 07:59:06 +0000 [thread overview]
Message-ID: <03a279d5ec9b258c30ddba01c14772ecb7e53cda.camel@ovgu.de> (raw)
Hi at all,
we run Proxmox-/Cephcluster on latest version (6.2-15 / 14.2.11) from
nosubscription-repo.
In the morning snapshots of 3 VMs were taken (VMs shutdown/off) but
only one snapshot of 1 VM is visible via webgui. All snapshots do exist
and are visible via pvesh and/or rbd snap list. There are although
entrys about snapshots in VM-config-files. All VMs run on same physical
host, log files do not show any special about that topic.
All physical hosts of the cluster were rebooted after snapshots were
taking - nothing changed.
Any hints about that?
best regards
--
Thomas Naumann
Abteilung Netze und Kommunikation
Otto-von-Guericke Universität Magdeburg
Universitätsrechenzentrum
Universitätsplatz 2
39106 Magdeburg
fon: +49 391 67-58563
email: thomas.naumann@ovgu.de
reply other threads:[~2020-11-23 8:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=03a279d5ec9b258c30ddba01c14772ecb7e53cda.camel@ovgu.de \
--to=thomas.naumann@ovgu.de \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox