Hi Vladislav,
On Mon, Jan 16, 2012 at 02:14:29PM +0300, Vladislav Bogdanov wrote:
> Hi Dejan,
>
> I'm evaluating crmsh in place of pacemaker bundled crm (because of
> rsc_ticket support).
>
> With current crmsh (b4b063507de0) it is impossible (ok, very hard) to
> manage cluster properties:
> # crm configure
> crm(live)configure# property [tab] ERROR: crmd:metadata: could not parse
> meta-data:
> ERROR: crmd:metadata: could not parse meta-data:
> ERROR: crmd:metadata: could not parse meta-data:
> ERROR: crmd:metadata: could not parse meta-data:
>
> Every subsequent [tab] press results in two more such lines printed.
> The same is after changing properties with crm configure edit.
How did you build crmsh? In particular, is this thing properly
replaced by autofoo:
crm_daemon_dir = "@GLUE_DAEMON_DIR@"
(that's in vars.py).
Does this work as expected:
crm ra info cmrd
If not, can you attach the output of
/usr/lib64/heartbeat/crmd metadata
Can you get the metadata from pengine:
crm ra info pengine
> Pacemaker is 41dedc0 (Dec 16). Bundled crm works perfectly (except
> rsc_ticket support ;) )
I don't see this issue with this Pacemaker:
CRM Version: 1.1.6 (b988976485d15cb702c9307df55512d323831a5e)
Thanks,
Dejan
> Hoping this can be easily fixed (something in ra.py.in? ),
>
> Best regards,
> Vladislav
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
