> I get this information in the cluster information:
> * drbd_database_monitor_0 on lisbon 'not installed' (5): call=20,
> status='complete', exitreason='DRBD kernel (module) not available?',
> last-rc-change='2021-01-08 18:03:10 +01:00', queued=0ms,
> exec=96ms
>
> The drbd-service is not start
Hi,
I'm trying to install a 2 node pacemaker/drbd cluster on a CentOS 8.3. I'm
using this versions:
kmod-drbd90-9.0.25-2.el8_3.elrepo.x86_64
drbd90-utils-9.13.1-1.el8.elrepo.x86_64
pacemaker-cluster-libs-2.0.4-6.el8.x86_64
pacemaker-cli-2.0.4-6.el8.x86_64
pacemaker-schemas-2.0.4-6.el8.noarch
pa
On Fri, 2021-01-08 at 11:46 +0100, Ulrich Windl wrote:
> Hi!
>
> Trying to reproduce a problem that had occurred in the past after a
> "crm resource refresh" ("reprobe"), I noticed something on the
> DC that looks odd to me:
>
> Jan 08 11:13:21 h16 pacemaker-controld[4478]: notice: Forcing the
Hi!
When editing my configuration I found this:
...
meta priority=123 allow-migrate=true target-role=Stopped \
meta 1: resource-stickiness=0 target-role=Stopped \
meta 2: rule 0: date spec hours=7-19 weekdays=1-5
resource-stickiness=1000
Note the multiple " target-role=St
Hi!
Trying to reproduce a problem that had occurred in the past after a "crm
resource refresh" ("reprobe"), I noticed something on the DC that looks odd to
me:
Jan 08 11:13:21 h16 pacemaker-controld[4478]: notice: Forcing the status of
all resources to be redetected
Jan 08 11:13:21 h16 pacem
Hi,
Thank you for reporting the issue and also for testing the fix so
quickly and confirming it works.
Regards,
Tomas
Dne 08. 01. 21 v 5:39 井上和徳 napsal(a):
Hi,
Thanks for your reply.
I've backported ddb0d3f to pcs-0.10.6-4.el8 and confirmed that this
bug is fixed.
Thanks,
Kazunori INOUE
