You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of 1/03/2024 Proxmox hosts fully patched using a ubuntu 23.x LXC within a python env and the current build of Proxmox-load-balancer of 1/03/2024. when I run the program after updating the config file with correct info I get.
(.env) root@prox-lb:/opt/Proxmox-load-balancer# python plb.py
INFO | START ***Load-balancer!***
Traceback (most recent call last):
File "/opt/Proxmox-load-balancer/plb.py", line 496, in <module>
main()
File "/opt/Proxmox-load-balancer/plb.py", line 466, in main
cluster = Cluster(server_url)
^^^^^^^^^^^^^^^^^^^
File "/opt/Proxmox-load-balancer/plb.py", line 96, in __init__
self.cl_nodes: dict = self.cluster_hosts() # All cluster nodes
^^^^^^^^^^^^^^^^^^^^
File "/opt/Proxmox-load-balancer/plb.py", line 169, in cluster_hosts
self.master_node = rr.json()['data']['manager_status']['master_node']
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^
KeyError: 'master_node'
I edit the plb.py to show the output of the rr.json() within the cluster_hosts(self) function and it showed the below output. there is no master_node key. I'm not sure if it's not required anymore of I have something changed in my cluster.. either way it's not working.
This is required if the script is installed on all nodes. In this case, only 1 should decide how to balance. And thus the HA master is selected. If you have 1 instance, this mechanism is not needed at all.
As of 1/03/2024 Proxmox hosts fully patched using a ubuntu 23.x LXC within a python env and the current build of Proxmox-load-balancer of 1/03/2024. when I run the program after updating the config file with correct info I get.
I edit the plb.py to show the output of the rr.json() within the cluster_hosts(self) function and it showed the below output. there is no master_node key. I'm not sure if it's not required anymore of I have something changed in my cluster.. either way it's not working.
Cluster Information
The text was updated successfully, but these errors were encountered: