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.8.0-rc.1
Date: Thu, 6 Feb 2025 10:47:20 +0100	[thread overview]
Message-ID: <Z6SFKGCHtKIgTTAv@arm64> (raw)

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

Dear DRBD users,

this is RC1 of the upcoming drbd-reactor version 1.8.0. All in all
reactor proved to do what it should, but there is one improvement for
the promoter plugin: We had a user that "drbd-reactorctl disabled" a
resource where the demotion of the DRBD device did not work for whatever
reason. Then the user enabled the resource again, but the services on
top were not started. The explanation is simple: The device was already
Primary, so drbd-reactor never saw a "may_promote:yes" in the events2
stream and well, did not react.

New behavior: On plugin start we generate the systemd target templates
as usual, but we also check if we are already local Primary. If so, we
also start the systemd target unit. This does not hurt and might help in
such "things half started" scenarios.

Please test, if we don't find any bugs the final release will happen in
about a week from now.

Regards, rck

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

Changelog:

[ Roland Kammerer ]
* doc: mv on-{stop,drbd-demote}-failure
* promoter: start services on activation
* doc,promoter: note about LINSTOR
* build: mv .cargo/config.{,toml}

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

                 reply	other threads:[~2025-02-06  9:47 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=Z6SFKGCHtKIgTTAv@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