Description
Failure to add a default bridge via the platform's web interface.
When the problem may occur:
- when manually configuring the node network;
-
when bridge statuses are incorrectly displayed on the Network Settings tab for cluster nodes with two network interfaces. If there is a default bridge, the interface displays a message about its absence. А message displayed stating that for correct network operation on the node the default bridge is to be added. Meanwhile, there is no link to add the device.
Fixed in version 2023.07.1. To resolve the error, we recommend upgrading to the current platform version.
Solution
There are potential risks involved in altering a database. We do not recommend making manual edits to the database, as it can disrupt the correct operation of the platform.
Create a backup of the platform before performing any actions with the database.
To resolve the issue, add the default bridge via the database:
- Connect to the server with the platform via SSH.
-
Connect to the DBMS:
docker exec -it mysql bash -c "mysql isp -p\$MYSQL_ROOT_PASSWORD"
-
Get the names and IDs of the bridge by running the query:
SELECT id, name FROM vm_node_bridge WHERE node = <node_id> ;
CommentExample output+----+-------+ | id | name | +----+-------+ | 97 | vmbr0 | +----+-------+ 1 row in set (0.00 sec)
-
Set the default bridge with the query:
UPDATE vm_node_bridge SET is_default = 1 WHERE id = <bridge_id> ;
Comment -
Make sure that the default bridge is set correctly. To do this, run the query:
select * from vm_node_bridge where node= <node_id>;
CommentExample output*************************** 1. row *************************** id: 97 name: vmbr0 node: 64 ipv4: 10.10.10.10/24 ipv6: NULL state: enabled is_default: 1 is_main_network: 1 vlan: 111 take_slave_ip: 0
The string is_default: 1 means that the bridge is set by default.