On Fri, Sep 29, 2023 at 12:51 AM Bartosz Kaczyński
wrote:
>
> Reid Wahl writes:
>
> > On Tue, Sep 19, 2023 at 9:10 AM Bartosz Kaczyński
> > wrote:
> >>
> >> Greetings,
> >>
> >> I am facing an issue with launching a primitive resource in a two-node
> >> Pacemaker/Corosync cluster. I have set up
Reid Wahl writes:
> On Tue, Sep 19, 2023 at 9:10 AM Bartosz Kaczyński
> wrote:
>>
>> Greetings,
>>
>> I am facing an issue with launching a primitive resource in a two-node
>> Pacemaker/Corosync cluster. I have set up a lab environment based on the
>> guidelines from the "Say Goodbye to Downtim
On Mon, Sep 25, 2023 at 4:50 PM Reid Wahl wrote:
>
> On Tue, Sep 19, 2023 at 9:10 AM Bartosz Kaczyński
> wrote:
> >
> > Greetings,
> >
> > I am facing an issue with launching a primitive resource in a two-node
> > Pacemaker/Corosync cluster. I have set up a lab environment based on the
> > guide
On Tue, Sep 19, 2023 at 9:10 AM Bartosz Kaczyński wrote:
>
> Greetings,
>
> I am facing an issue with launching a primitive resource in a two-node
> Pacemaker/Corosync cluster. I have set up a lab environment based on the
> guidelines from the "Say Goodbye to Downtime with SUSE Linux Enterprise
>
Greetings,
I am facing an issue with launching a primitive resource in a two-node
Pacemaker/Corosync cluster. I have set up a lab environment based on the
guidelines from the "Say Goodbye to Downtime with SUSE Linux Enterprise
Server (Repeat)" [1] course.
In my lab environment, I am using openSUS