On Thu, Sep 13, 2012 at 09:14:07PM +0300, Vladislav Bogdanov wrote:
13.09.2012 15:42, Dejan Muhamedagic wrote:
Hi again,
On Thu, Sep 13, 2012 at 02:57:54PM +0300, Vladislav Bogdanov wrote:
Hi Dejan, all,
current crm shell (b58a3398bf11) can not parse node 'id' attribute when
Hi Dejan, all,
current crm shell (b58a3398bf11) can not parse node 'id' attribute when
running on corosync 2:
# crm configure show |grep xml
INFO: object 1074005258 cannot be represented in the CLI notation
INFO: object 1090782474 cannot be represented in the CLI notation
INFO: object 1107559690
Hi again,
On Thu, Sep 13, 2012 at 02:57:54PM +0300, Vladislav Bogdanov wrote:
Hi Dejan, all,
current crm shell (b58a3398bf11) can not parse node 'id' attribute when
running on corosync 2:
# crm configure show |grep xml
INFO: object 1074005258 cannot be represented in the CLI notation
13.09.2012 15:37, Dejan Muhamedagic wrote:
Hi,
On Thu, Sep 13, 2012 at 02:57:54PM +0300, Vladislav Bogdanov wrote:
Hi Dejan, all,
current crm shell (b58a3398bf11) can not parse node 'id' attribute when
running on corosync 2:
# crm configure show |grep xml
INFO: object 1074005258 cannot
On Thu, Sep 13, 2012 at 04:15:10PM +0300, Vladislav Bogdanov wrote:
13.09.2012 15:37, Dejan Muhamedagic wrote:
Hi,
On Thu, Sep 13, 2012 at 02:57:54PM +0300, Vladislav Bogdanov wrote:
Hi Dejan, all,
current crm shell (b58a3398bf11) can not parse node 'id' attribute when
running on
13.09.2012 15:42, Dejan Muhamedagic wrote:
Hi again,
On Thu, Sep 13, 2012 at 02:57:54PM +0300, Vladislav Bogdanov wrote:
Hi Dejan, all,
current crm shell (b58a3398bf11) can not parse node 'id' attribute when
running on corosync 2:
# crm configure show |grep xml
INFO: object 1074005258