Bonding LACP web configuration seems broken in V. 2.4
Lewis
2 Posts
February 16, 2020, 9:51 pmQuote from Lewis on February 16, 2020, 9:51 pmThere is much backstory, but after beating my head against a wall I finale made a window... 🙂
(short version)
When setting up bonding for backend 1 & 2 on [step 3] in the web configuration it list several bond modes.
I need 802.3ad (LACP). That is how our current working cluster is setup.
The problem arises when the configuration file /opt/petasan/config/cluster_info.json is written with that exact web selection.
"mode": "802.3ad (LACP)"
This seems to break bond creation after [step 6].
I probably did it the hard way, but here is how I "fixed" it.
After PetaSAN 2.4 is installed on you first node, from the blue screen enter the bash shell, then edit enums.py
vi /usr/lib/python2.7/dist-packages/PetaSAN/core/common/enums.py
Under the class BondMode the line:
mode_802_3_ad = "802.3ad (LACP)"
should be :
mode_802_3_ad = "802.3ad"
save it then reboot.
When configuring with the web interface the new selection is correct and when the config file is written it is correct as well:
"mode": "802.3ad"
and the bonding works...
At least for me...
There is much backstory, but after beating my head against a wall I finale made a window... 🙂
(short version)
When setting up bonding for backend 1 & 2 on [step 3] in the web configuration it list several bond modes.
I need 802.3ad (LACP). That is how our current working cluster is setup.
The problem arises when the configuration file /opt/petasan/config/cluster_info.json is written with that exact web selection.
"mode": "802.3ad (LACP)"
This seems to break bond creation after [step 6].
I probably did it the hard way, but here is how I "fixed" it.
After PetaSAN 2.4 is installed on you first node, from the blue screen enter the bash shell, then edit enums.py
vi /usr/lib/python2.7/dist-packages/PetaSAN/core/common/enums.py
Under the class BondMode the line:
mode_802_3_ad = "802.3ad (LACP)"
should be :
mode_802_3_ad = "802.3ad"
save it then reboot.
When configuring with the web interface the new selection is correct and when the config file is written it is correct as well:
"mode": "802.3ad"
and the bonding works...
At least for me...
admin
2,930 Posts
February 17, 2020, 11:24 amQuote from admin on February 17, 2020, 11:24 amThank you foe spotting this 🙂 it looks like a recent ui bug.
Thank you foe spotting this 🙂 it looks like a recent ui bug.
Bonding LACP web configuration seems broken in V. 2.4
Lewis
2 Posts
Quote from Lewis on February 16, 2020, 9:51 pmThere is much backstory, but after beating my head against a wall I finale made a window... 🙂
(short version)
When setting up bonding for backend 1 & 2 on [step 3] in the web configuration it list several bond modes.
I need 802.3ad (LACP). That is how our current working cluster is setup.
The problem arises when the configuration file /opt/petasan/config/cluster_info.json is written with that exact web selection.
"mode": "802.3ad (LACP)"
This seems to break bond creation after [step 6].
I probably did it the hard way, but here is how I "fixed" it.
After PetaSAN 2.4 is installed on you first node, from the blue screen enter the bash shell, then edit enums.py
vi /usr/lib/python2.7/dist-packages/PetaSAN/core/common/enums.py
Under the class BondMode the line:
mode_802_3_ad = "802.3ad (LACP)"
should be :
mode_802_3_ad = "802.3ad"
save it then reboot.
When configuring with the web interface the new selection is correct and when the config file is written it is correct as well:
"mode": "802.3ad"
and the bonding works...
At least for me...
There is much backstory, but after beating my head against a wall I finale made a window... 🙂
(short version)
When setting up bonding for backend 1 & 2 on [step 3] in the web configuration it list several bond modes.
I need 802.3ad (LACP). That is how our current working cluster is setup.
The problem arises when the configuration file /opt/petasan/config/cluster_info.json is written with that exact web selection.
"mode": "802.3ad (LACP)"
This seems to break bond creation after [step 6].
I probably did it the hard way, but here is how I "fixed" it.
After PetaSAN 2.4 is installed on you first node, from the blue screen enter the bash shell, then edit enums.py
vi /usr/lib/python2.7/dist-packages/PetaSAN/core/common/enums.py
Under the class BondMode the line:
mode_802_3_ad = "802.3ad (LACP)"
should be :
mode_802_3_ad = "802.3ad"
save it then reboot.
When configuring with the web interface the new selection is correct and when the config file is written it is correct as well:
"mode": "802.3ad"
and the bonding works...
At least for me...
admin
2,930 Posts
Quote from admin on February 17, 2020, 11:24 amThank you foe spotting this 🙂 it looks like a recent ui bug.
Thank you foe spotting this 🙂 it looks like a recent ui bug.