Distributed Replicated Block Device (DRBD) announcements
 help / color / mirror / Atom feed
From: Roland Kammerer <roland.kammerer@linbit.com>
To: drbd-announce@lists.linbit.com, drbd-user@lists.linbit.com
Subject: drbd-reactor v1.6.0-rc.1
Date: Fri, 15 Nov 2024 12:37:12 +0100	[thread overview]
Message-ID: <ZzcyaNvToIPqp_2M@arm64> (raw)

[-- Attachment #1: Type: text/plain, Size: 1433 bytes --]

Dear DRBD users,

this is the first RC of the upcoming 1.6.0 release. It has some
additional features like only generating overrides when necessary
instead of empty overrides. Due to recent changes in drbd-utils we no
longer need to override ExecCondition to ExecStart unconditionally,
which produces nicer status output on newer systems.

The main reason for the release is that newer drbd-utils expose a new
keyword (i.e., "open") in the events2 stream, and we now added that to
reactor. Without that the reactor log is spammed with warnings which are
actually harmless. We also changed these log messages from level warn to
debug.

As the changes are pretty minimal and the real reason for this release
is to get the "open" keyword into the parser, this will probably be a
short RC phase with a final release mid next week. So if you want to
help testing, please do so early.

Regards, rck

GIT: https://github.com/LINBIT/drbd-reactor/commit/1b0de0d6eba68d27f3f906030de67aa397503995
TGZ: https://pkg.linbit.com//downloads/drbd/utils/drbd-reactor-1.6.0-rc.1.tar.gz
PPA: https://launchpad.net/~linbit/+archive/ubuntu/linbit-drbd9-stack

Changelog:
[ Moritz Wanzenböck ]
* umh: fix wrong environment variable name
* events: add "open" to device keywords

[ Roland Kammerer ]
* promoter: do not generate ExecStart override
* promoter: write overrides if necessary
* events: missing keywords -> debug

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

                 reply	other threads:[~2024-11-15 11:37 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=ZzcyaNvToIPqp_2M@arm64 \
    --to=roland.kammerer@linbit.com \
    --cc=drbd-announce@lists.linbit.com \
    --cc=drbd-user@lists.linbit.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