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

[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, which seems like it could easily be
an exported symbol / API / ABI.

afaict, there would be no harm in leaving this struct member in place,
but now unused, in the backported patch. The replacement, in the code,
is to pass this struct member in the callers themselves, but this in
turn changed the callback layout, which again might be part of the
exported interface of the library.

How easy is this to reproduce? Do you have a testcase handy that I might
be able to run?

-- 
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 pacemaker to fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1740892/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[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, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1740892

Title:
  corosync upgrade on 2018-01-02 caused pacemaker to fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1740892/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[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.
> https://bugs.launchpad.net/bugs/1722936
>
> Title:
>   sssd hbac rule applicaton for AD users is inconsistent
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1722936/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to sssd in Ubuntu.
https://bugs.launchpad.net/bugs/1722936

Title:
  sssd hbac rule applicaton for AD users is inconsistent

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1722936/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

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

[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 pacemaker to fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1740892/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs