After configuring it with "Configure Network" in hpe-vm, the device is not deleted even if

[kurotan]

After configuring it with "Configure Network" in hpe-vm, the device is not deleted even if it is deleted.

I deleted the network (router) settings from the manager, but when I run "ip a", the network settings seem to remain.

/etc/netplan/60-mvm.yaml does not seem to contain the settings from the manager.

It seems like they remain in a different configuration file, but I don't know what the cause is.

In this state, I tried to reconfigure the router using the same bond device, but an error occurred and I was unable to do so.
The cause seemed to be that the network remained.

There was a log in Health that seemed to be due to the settings remaining.
Previously configured router name: backend10g1
Currently configured router name: backend1g1

[RxCachedThreadScheduler-6] Unable to provision router on Host: host-name - hpe-vm-cluster: null - Unable to add ovs port bond2 to bridge backend1g1: ovs-vsctl: cannot create a port named bond2 because a port named bond2 already exists on bridge backend10g1

[Ranveer]

Hello Kurotan,

Few days ago we received one query:
"Creating bridge network router manually in ui doesnt update the netplan files in kvm-hosts"

Below  was the explaiantion from Engineering:

The issue you're reporting is actually expected behavior. When creating bridge networks (routers) manually through the VME UI after initial cluster setup, these bridges are intentionally created in Open vSwitch (OVS) and not in netplan. You can verify this by running the command
ovs-vsctl list-br which will show all the bridges created.

To explain further:
The Management bridge is the only bridge created with netplan during VME creation, as this bridge needs to share interfaces with the underlying OS, not just for KVM use
Additional bridges created after cluster setup are handled through OVS
For any new interfaces that will be consumed by these bridges, you will need to manually set them up in netplan, but the bridge itself will not appear in the netplan configuration

This design is intentional and consistent across our releases, including 8.0.3, 8.0.4, and 8.0.5.

By the way, are you able to get see bridge on hypervisor Host?
#ovs-vsctl show
#virsh net-list --all
If need to know more about a network.
#virsh net-info <Name from net-list>

Regards
Ranveer

[kurotan]

Thank you for your reply.

The command results are shown below.

The bridge that I deleted from the manager is definitely still there.

ーーーーーーーーーーーーーーーーーーーーーーーーーーーーーーー

root@ucs-3:/var/morpheus/kvm/config# ovs-vsctl show
881da7ef-2da0-4555-afde-f13632eb3411
Bridge backend10g1
Port bond2
Interface bond2
Port backend10g1
Interface backend10g1
type: internal
Bridge backend10g2
Port backend10g2
Interface backend10g2
type: internal
Port bond3
Interface bond3
Bridge backend
fail_mode: standalone
Port backend
Interface backend
type: internal
Port bond1
Interface bond1
Bridge backend1g1
Port backend1g1
Interface backend1g1
type: internal
Bridge mgmt
fail_mode: standalone
Port mgmt
Interface mgmt
type: internal
Port bond0
Interface bond0
Port vnet0
Interface vnet0
ovs_version: "3.3.0"

root@ucs-3:/var/morpheus/kvm/config# virsh net-list --all
Name State Autostart Persistent
-----------------------------------------------
Backend active yes yes
Compute active yes yes
Management active yes yes

ーーーーーーーーーーーーーーーーーーーーーーーーーーーーーーー

Will deleting unnecessary settings solve the problem?
If possible, please tell me the command.

And,An xml file was also left in "/var/morpheus/kvm/config".

Is it okay to delete unnecessary configuration files (xml)?

[Ranveer]

Hello Kurtoan,

From command prompt the Bridge can be deleted using 
#ovs-vsctl del-br <bridge_name>

Please do not delete first Bridge "mgmt"