[Pacemaker] Fwd: Bug#612682: pacemaker: inconistent configuration behaviour in crm stonith:ssh setup

Simon Horman horms at verge.net.au
Wed Feb 9 23:51:39 UTC 2011


Hi Pacemaker upstream people,

could someone comment on this bug report.

The bug report can be seen at http://bugs.debian.org/612682
CCing 612682 at bugs.debian.org should append any responses
to the but report.

Thanks

----- Forwarded message from Michael Prokop <mika at debian.org> -----

Date: Wed, 09 Feb 2011 23:34:39 +0100
From: Michael Prokop <mika at debian.org>
To: Debian Bug Tracking System <submit at bugs.debian.org>
Subject: Bug#612682: pacemaker: inconistent configuration behaviour in crm
	stonith:ssh setup
Resent-From: Michael Prokop <mika at debian.org>

Package: pacemaker
Version: 1.0.9.1+hg15626-1
Severity: normal


Please compare (notice the "ERROR: ssh-stonith: parameter foo-host2
does not exist"):

  # crm configure primitive ssh-stonith stonith:ssh params hostlist="foo-host1 foo-host2" op monitor interval=60s
  ERROR: ssh-stonith: parameter foo-host2 does not exist
  WARNING: ssh-stonith: default timeout 20s for start is smaller than the advised 60
  WARNING: ssh-stonith: default timeout 20s for monitor_0 is smaller than the advised 60
  Do you still want to commit? Ctrl-C, leaving

with:

  # crm configure
  crm(live)configure# primitive ssh-stonith stonith:ssh params hostlist="foo-host1 foo-host2" op monitor interval=60s
  WARNING: ssh-stonith: default timeout 20s for start is smaller than the advised 60
  WARNING: ssh-stonith: default timeout 20s for monitor_0 is smaller than the advised 60
  crm(live)configure# quit
  There are changes pending. Do you want to commit them? yes
  WARNING: ssh-stonith: default timeout 20s for start is smaller than the advised 60
  WARNING: ssh-stonith: default timeout 20s for monitor_0 is smaller than the advised 60
  bye

JFTR:

  # crm configure show
  [...]
  primitive ssh-stonith stonith:ssh \
          params hostlist="foo-host1 foo-host2" \
          op monitor interval="60s"
  [...]

The parameter parsing looks like a bug to me. It works as expected
in the interactive shell but when being invoked directly in one
single command from "outside" it complains with above mentioned
"ERROR: ssh-stonith: parameter [...] does not exist" message which
is misleading. JFTR: when accepting through "Do you still want to
commit?" it works as well of course.

regards,
-mika-




----- End forwarded message -----




More information about the Pacemaker mailing list