Hi all,
It has been discovered that newer versions of selinux-policy prevent
bundles in pacemaker 2.0 from logging. I have a straightforward fix,
but it means that whenever a cluster is upgraded from pre-2.0.3 to
2.0.3 or later, all active bundles will restart once the last older
node leaves the c
On 06/06/2019 23:34, Ken Gaillot wrote:
> Hi all,
>
> It has been discovered that newer versions of selinux-policy prevent
> bundles in pacemaker 2.0 from logging. I have a straightforward fix,
> but it means that whenever a cluster is upgraded from pre-2.0.3 to
> 2.0.3 or later, all active bundles
ject: [ClusterLabs] Possible intrusive change in bundles for 2.0.3
>
> Hi all,
>
> It has been discovered that newer versions of selinux-policy prevent bundles
> in pacemaker 2.0 from logging. I have a straightforward fix, but it means that
> whenever a cluster is upgraded from pre-2
On Fri, 2019-06-07 at 10:15 +0100, lejeczek wrote:
> On 06/06/2019 23:34, Ken Gaillot wrote:
> > Hi all,
> >
> > It has been discovered that newer versions of selinux-policy
> > prevent
> > bundles in pacemaker 2.0 from logging. I have a straightforward
> > fix,
> > but it means that whenever a cl
35 PM
> > To: Cluster Labs - All topics related to open-source clustering
> > welcomed
> >
> > Subject: [ClusterLabs] Possible intrusive change in bundles for
> > 2.0.3
> >
> > Hi all,
> >
> > It has been discovered that newer versions of selin
