Hi Reid,
Hi Steffen,
> According to Steffen's description, the "pending" is displayed
> only on
> node 1, while the DC is node 3. That's another thing that makes me
> wonder if this is a distinct issue.
The problem may not be the same.
I think it's a good idea to have bugzilla or ML provide
On Wed, Jan 6, 2021 at 11:07 PM wrote:
>
> Hi Steffen,
> Hi Reid,
>
> I also checked the Centos source rpm and it seems to include a fix for the
> problem.
>
> As Steffen suggested, if you share your CIB settings, I might know something.
>
> If this issue is the same as the fix, the display will
If there will only ever be one value (e.g., "httpserver") in the file,
then yet another possibility is to use an ocf:heartbeat:symlink
resource. You could set up a file on each node (say,
/var/local/project/cluster-node-real) with "httpserver" as its
contents. Then create a symlink resource with
yes, my bad. Sorry :)
On Thu, Jan 7, 2021 at 8:04 AM Reid Wahl wrote:
>
> Steffen, did you mean to reply to a different thread? I ask because
> there's another active one and you haven't been involved in this one
> yet :)
>
> On Wed, Jan 6, 2021 at 11:01 PM Steffen Vinther Sørensen
> wrote:
> >
Hi Steffen,
Hi Reid,
I also checked the Centos source rpm and it seems to include a fix for the
problem.
As Steffen suggested, if you share your CIB settings, I might know something.
If this issue is the same as the fix, the display will only be displayed on the
DC node and will not affect
Steffen, did you mean to reply to a different thread? I ask because
there's another active one and you haven't been involved in this one
yet :)
On Wed, Jan 6, 2021 at 11:01 PM Steffen Vinther Sørensen
wrote:
>
> No I don't set that, and its not showing up in output of 'pcs stonith
> show --full'
No I don't set that, and its not showing up in output of 'pcs stonith
show --full'
On Thu, Jan 7, 2021 at 7:46 AM Reid Wahl wrote:
>
> Do you have pcmk_monitor_timeout set? Ken mentioned that the start
> operation includes a registration and a status call. There was a bug
> in which the status
It's supposedly fixed in that version.
- https://bugzilla.redhat.com/show_bug.cgi?id=1787749
- https://access.redhat.com/solutions/4713471
So you may be hitting a different issue (unless there's a bug in the
pcmk 1.1 backport of the fix).
I may be a little bit out of my area of knowledge
Hi Hideo,
If the fix is not going to make it into the CentOS7 pacemaker version,
I guess the stable approach to take advantage of it is to build the
cluster on another OS than CentOS7 ? A little late for that in this
case though :)
Regards
Steffen
On Thu, Jan 7, 2021 at 7:27 AM wrote:
>
>
Do you have pcmk_monitor_timeout set? Ken mentioned that the start
operation includes a registration and a status call. There was a bug
in which the status call used the pcmk_monitor_timeout (if set), but
the start operation that triggered it used the default timeout. So if
the
Hi Reid,
Pacemaker version is the same on all 3 nodes, CentOS7 most recent update :
# pacemakerd --version
Pacemaker 1.1.23-1.el7_9.1
Written by Andrew Beekhof
# rpm -qa | grep pacemaker
pacemaker-cluster-libs-1.1.23-1.el7_9.1.x86_64
pacemaker-cli-1.1.23-1.el7_9.1.x86_64
Hi Steffen,
The fix pointed out by Reid is affecting it.
Since the fencing action requested by the DC node exists only in the DC node,
such an event occurs.
You will need to take advantage of the modified pacemaker to resolve the issue.
Best Regards,
Hideo Yamauchi.
- Original Message
Hi, Steffen. Are your cluster nodes all running the same Pacemaker
versions? This looks like Bug 5401[1], which is fixed by upstream
commit df71a07[2]. I'm a little bit confused about why it only shows
up on one out of three nodes though.
[1] https://bugs.clusterlabs.org/show_bug.cgi?id=5401
[2]
Hi Ulrich,
Could you please help to verify this issue? Package from
https://build.opensuse.org/package/show/home:XinLiang:crmsh_testing2/crmsh
Thank you!
Regards,
xin
From: Users on behalf of Ulrich Windl
Sent: Thursday, December 17, 2020 3:03 PM
To:
14 matches
Mail list logo
