[Pacemaker] crm: timeout for start warning (possible bug?)
Dejan Muhamedagic
dejanmm at fastmail.fm
Tue Jan 26 13:31:58 UTC 2010
Hi,
On Tue, Jan 26, 2010 at 12:39:35PM +0000, Maros Timko wrote:
> Hi all,
>
> I think the start timeout check has indirectly introduced some bug.
>
> I have already a group with Filesystem primitive in it:
> group dom0 dom0-drbd-Domain00 dom0-fs-Domain00 dom0-vsppreconsole \
> meta is-managed="true"
>
> I want to create a new group from primitives that already exist:
> crm(live)configure# group udom udom-drbd-udom0 udom-drbd-udom1
> udom-drbd-udom2 udom-delay udom-delay udom-vm meta is-managed=false
> crm(live)configure# commit
> WARNING: dom0-fs-Domain00: timeout 20s for start is smaller than the advised
> 60
> Traceback (most recent call last):
> File "/usr/sbin/crm", line 7561, in ?
> try: parse_line(levels,shlex.split(inp))
> File "/usr/sbin/crm", line 7437, in parse_line
> rv = d() # execute the command
> File "/usr/sbin/crm", line 7436, in <lambda>
> d = lambda: cmd[0](*args)
> File "/usr/sbin/crm", line 2977, in commit
> rc2 = self.verify("verify")
> File "/usr/sbin/crm", line 2882, in verify
> rc2 = set_obj.verify2()
> File "/usr/sbin/crm", line 5219, in verify2
> rc |= obj.check_sanity()
> File "/usr/sbin/crm", line 5735, in check_sanity
> ra_type = self.node.getAttribute("type")
> File "/usr/lib64/python2.4/site-packages/_xmlplus/dom/minidom.py", line
> 685, in getAttribute
> return self._attrs[attname].value
> TypeError: unsubscriptable object
Indeed it looks like a bug. But I can't reproduce it here with
python v2.6. It is strange that there's an exception in
minidom's getAttribute.
Can you please open a bugzill and attach your CIB so I can check
where's the problem. Please also add information about the
distribution and python version.
Thanks,
Dejan
>
> From command line:
> crm configure group udom udom-drbd-udom0 udom-drbd-udom1 udom-drbd-udom2
> udom-delay udom-delay udom-vm meta is-managed=false
> WARNING: dom0-fs-Domain00: timeout 20s for start is smaller than the advised
> 60
> - the group is not created.
>
> So the check of the first group prevents me to create a new group.
> Interestingly the first group creation also reported warning, but the group
> itself was created.
>
> With regards,
> Tino
> _______________________________________________
> Pacemaker mailing list
> Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
More information about the Pacemaker
mailing list