From: Uwe Sauter <uwe.sauter.de@gmail.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] [update available] Re: Caution: ceph-mon service does not start after today's updates
Date: Thu, 26 Nov 2020 20:54:59 +0100 [thread overview]
Message-ID: <961e6e45-6345-793d-74e2-e16db96a4a70@gmail.com> (raw)
In-Reply-To: <32d89f84-29a7-90c4-deed-1a3638c99098@proxmox.com>
Thomas,
thank you and your team for that prompt response.
I'll try out tomorrow first thing in the morning.
Regards,
Uwe
Am 26.11.20 um 20:35 schrieb Thomas Lamprecht:
> Hi all,
> Hi Uwe and Lindsay,
>
> ceph 14.2.15-pve2 is now available, it includes fixes for the ordering
> restraints of the various ceph service unit files[0], besides that there
> where zero actual code changes.
>
> Due to that and Stoiko's tests (much thanks for all the help!) confirming
> the positive result of mine, we uploaded it for general availability.
>
> Thanks also to you two for reporting!
>
> regards,
> Thomas
>
> [0]: https://git.proxmox.com/?p=ceph.git;a=blob;f=patches/0009-fix-service-ordering-avoid-Before-remote-fs-pre.targ.patch;h=8fe5a35c385f7d4007b4965d297fc0daa9091be3;hb=99b3812832d5d5a8ac48a2e3b084c0ecf1fd087c
>
>
next prev parent reply other threads:[~2020-11-26 19:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 12:18 [PVE-User] " Uwe Sauter
2020-11-26 14:10 ` Lindsay Mathieson
2020-11-26 14:15 ` Uwe Sauter
2020-11-26 14:46 ` Thomas Lamprecht
2020-11-26 15:03 ` Lindsay Mathieson
2020-11-26 16:14 ` Thomas Lamprecht
2020-11-26 16:35 ` Thomas Lamprecht
2020-11-26 18:56 ` Thomas Lamprecht
2020-11-26 19:35 ` [PVE-User] [update available] " Thomas Lamprecht
2020-11-26 19:54 ` Uwe Sauter [this message]
2020-11-27 0:53 ` Lindsay Mathieson
2020-11-27 8:19 ` Uwe Sauter
2020-11-27 13:18 ` Lindsay Mathieson
2020-11-27 13:29 ` Jean-Luc Oms
2020-11-27 13:31 ` Lindsay Mathieson
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=961e6e45-6345-793d-74e2-e16db96a4a70@gmail.com \
--to=uwe.sauter.de@gmail.com \
--cc=pve-user@lists.proxmox.com \
--cc=t.lamprecht@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