[Pacemaker] crm: timeout for start warning (possible bug?)

[Maros Timko]

> >
> > 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.
>

The python version is visible in the trace, particularly it is
python-2.4.3-27 from CentOS 5.4 distribution.
So it probably makes no sence to file it as a bug. It is rather a
dependency issue.
Do you think there is a lot of crm code depending on this python
version 2.6 or something? I was running older Pacemakers with python
2.4 without any hassle.

> 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
>