On 2021-07-26 12:50 p.m.,
kgail...@redhat.com wrote:
On Mon, 2021-07-26 at 12:25 -0400, Digimer wrote:
On 2021-07-26 9:54 a.m., kgail...@redhat.com wrote:
On Fri, 2021-07-23 at 21:46 -0400, Digimer wrote:
On Mon, 2021-07-26 at 12:25 -0400, Digimer wrote:
> On 2021-07-26 9:54 a.m., kgail...@redhat.com wrote:
> > On Fri, 2021-07-23 at 21:46 -0400, Digimer wrote:
> > > After a LOT of hassle, I finally got it updated, but OMG it was
> > > painful.
> > >
> > > I degraded the cluster (unsure if needed),
On 2021-07-26 9:54 a.m.,
kgail...@redhat.com wrote:
On Fri, 2021-07-23 at 21:46 -0400, Digimer wrote:
After a LOT of hassle, I finally got it updated, but OMG it was
painful.
I degraded the cluster (unsure if needed), set maintenance mode,
deleted
On 2021-07-26 9:54 a.m.,
kgail...@redhat.com wrote:
On Fri, 2021-07-23 at 21:46 -0400, Digimer wrote:
After a LOT of hassle, I finally got it updated, but OMG it was
painful.
I degraded the cluster (unsure if needed), set maintenance mode,
deleted
On Fri, 2021-07-23 at 21:46 -0400, Digimer wrote:
> After a LOT of hassle, I finally got it updated, but OMG it was
> painful.
>
> I degraded the cluster (unsure if needed), set maintenance mode,
> deleted
> the stonith levels, deleted the stonith devices, recreated them with
> the
> updated
After a LOT of hassle, I finally got it updated, but OMG it was painful.
I degraded the cluster (unsure if needed), set maintenance mode, deleted
the stonith levels, deleted the stonith devices, recreated them with the
updated values, recreated the stonith levels, and finally disabled
maintenance
Update;
Appears I can't even delete the damn things. They re-appeared after
doing a [pcs stonith remove '!.
Wow.
digimer
On 2021-07-23 7:56 p.m., Digimer wrote:
> Hi all,
>
> Got a really odd one here...
>
> I had a cluster in the lab where it was built and tested. Then we
> deployed
Hi all,
Got a really odd one here...
I had a cluster in the lab where it was built and tested. Then we
deployed it, and I've been trying to update the stonith config. It
_seems_ to take at first, then it reverts back to the old config. This
is super annoying, obviously. :)
So I can confirm
