Proxmox LACP Corosync

[willifehler]

Hey there,

I have an issue after an LACP deployment.
Before I execute my Ansible Playbook:

root@pve001:~# pvecm status
Cluster information
-------------------
Name:             test
Config Version:   2
Transport:        knet
Secure auth:      on

Quorum information
------------------
Date:             Fri Aug  2 10:54:15 2024
Quorum provider:  corosync_votequorum
Nodes:            2
Node ID:          0x00000001
Ring ID:          1.16
Quorate:          Yes

Votequorum information
----------------------
Expected votes:   2
Highest expected: 2
Total votes:      2
Quorum:           2
Flags:            Quorate

Membership information
----------------------
    Nodeid      Votes Name
0x00000001          1 ... (local)
0x00000002          1 ...

After my Ansible LACP deployment:

pve001:

root@pve001:~# pvecm status
Cluster information
-------------------
Name:             test
Config Version:   2
Transport:        knet
Secure auth:      on

Quorum information
------------------
Date:             Fri Aug  2 11:05:08 2024
Quorum provider:  corosync_votequorum
Nodes:            1
Node ID:          0x00000001
Ring ID:          1.1b
Quorate:          No

Votequorum information
----------------------
Expected votes:   2
Highest expected: 2
Total votes:      1
Quorum:           2 Activity blocked
Flags:

Membership information
----------------------
    Nodeid      Votes Name
0x00000001          1 ... (local)

pve002:

root@pve002:~# pvecm status
Cluster information
-------------------
Name:             test
Config Version:   2
Transport:        knet
Secure auth:      on

Quorum information
------------------
Date:             Fri Aug  2 11:05:44 2024
Quorum provider:  corosync_votequorum
Nodes:            1
Node ID:          0x00000002
Ring ID:          2.1f
Quorate:          No

Votequorum information
----------------------
Expected votes:   2
Highest expected: 2
Total votes:      1
Quorum:           2 Activity blocked
Flags:

Membership information
----------------------
    Nodeid      Votes Name
0x00000002          1 ... (local)

Do I need to change something in Corosync?

Regards - Willi

 

[LnxBil]

I have an issue after an LACP deployment.

What issue? I don't see an error message, just a split brain of a (not supported) two node cluster.

Do I need to change something in Corosync?

we nee more information.

What did you change and how? Just stating that it does not work and the output of a split brain does really not help to help you.

 

[esi_y]

I have an issue after an LACP deployment.
Before I execute my Ansible Playbook:

What's in the playbook? What's the topology?

After my Ansible LACP deployment:

pve001:

root@pve001:~# pvecm status
Cluster information
-------------------
Name:             test
Config Version:   2
Transport:        knet
Secure auth:      on

Quorum information
------------------
Date:             Fri Aug  2 11:05:08 2024
Quorum provider:  corosync_votequorum
Nodes:            1
Node ID:          0x00000001
Ring ID:          1.1b
Quorate:          No

Votequorum information
----------------------
Expected votes:   2
Highest expected: 2
Total votes:      1
Quorum:           2 Activity blocked
Flags:

Membership information
----------------------
    Nodeid      Votes Name
0x00000001          1 ... (local)

What's in the log at the time of you running the playbook?

 

[esi_y]

(not supported)

two node cluster.

But that's not related to LACP, is it?