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: prepare v1.8.0-rc.1 · LINBIT/drbd-reactor@7a6f9c2 · GitHub
TGZ: https://pkg.linbit.com//downloads/drbd/utils/drbd-reactor-1.8.0-rc.1.tar.gz
PPA: LINBIT DRBD9 Stack : “LINBIT” team
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}