From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: [pve-devel] applied: Re: [PATCH manager] ceph: extend error for wrong config-file link
Date: Fri, 18 Dec 2020 17:52:04 +0100 [thread overview]
Message-ID: <7e51673f-bf52-2081-4c81-38ac84bd7b25@proxmox.com> (raw)
In-Reply-To: <20201216114611.22178-1-s.ivanov@proxmox.com>
On 16/12/2020 12:46, Stoiko Ivanov wrote:
> Since I had to look up the cause of the error-message in our source
> explaining why exactly ceph-operations fail, because
> /etc/ceph/ceph.conf exists.
>
> reported via our community forum:
> https://forum.proxmox.com/threads/osd-ersetzen-neu-erstellen.80793/
>
> quickly tested on a virtual ceph cluster
>
> Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
> ---
> PVE/Ceph/Tools.pm | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
applied, thanks!
prev parent reply other threads:[~2020-12-18 16:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 11:46 [pve-devel] " Stoiko Ivanov
2020-12-18 16:52 ` Thomas Lamprecht [this message]
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=7e51673f-bf52-2081-4c81-38ac84bd7b25@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.ivanov@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