[Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

2018-01-03 Thread Nish Aravamudan
@afreiberger, thank you for the extra info! Reading the upstream patch referred to in Bug 1739033, I see this change: struct main_cp_cb_data { - enum main_cp_cb_data_state state; - int ringnumber; char *bindnetaddr; char *mcastaddr; Now, that is a struct size change

[Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

2018-01-03 Thread Nish Aravamudan
Hello, Being relatively new to pacemaker/corosync -- what is the actual error condition here? That when corosync is stopped (as part of the package upgrade), pacemakerd stops and does not restart? Thanks, Nish -- You received this bug notification because you are a member of Ubuntu Server Team,

Re: [Bug 1722936] Re: sssd hbac rule applicaton for AD users is inconsistent

2018-01-03 Thread Andreas Hasenack
Thanks Timo, will do. On Wed, Jan 3, 2018 at 6:50 AM, Timo Aaltonen wrote: > please file bugs for RH'isms you find in freeipa, I have no AD to test > against > > that said, 4.6.2 will soon hit bionic > > -- > You received this bug notification because you are subscribed to sssd in > Ubuntu. > ht

[Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

2018-01-03 Thread James Page
bug 1739033 was the stable release update that went in around this time. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1740892 Title: corosync upgrade on 2018-01-02 caused pacema