On 20/05/2021 10:42, Yedidyah Bar David wrote:
On Wed, May 19, 2021 at 9:34 PM lejeczek via Users <users@ovirt.org> wrote:
Hi guys.
-> $ ovirt-hosted-engine-cleanup -q
says it ran its stuff, done & dusted yet I see 'ovirtmgmt' bridge remains. Would that be a bug and how to clean it? It won't be fixed, because it's hard to fix _reliably_.
Most recent relevant patch: https://gerrit.ovirt.org/c/ovirt-hosted-engine-setup/+/112336 .
Basically, you have three choices:
1. Reinstall the OS and try again to deploy.
2. Try to deploy again without removing the bridge. If the failure was not due to misconfigured networking, and you handled the root cause for it, a second attempt will likely succeed.
3. Manually remove it:
- Make sure you can login to the machine even with the network down. From a serial console, remote KVM, whatever.
- Check which nic is inside the ovirtmgmt bridge.
- Note the IP address of the bridge.
- Remove the nic from the bridge, remove the bridge, configure the NIC to have the IP address. Or perhaps start it and let it get an address from dhcp, as applicable. 'ovirtmgmt' survives reboots or rather - even after manual removal, after reboot it gets created anew. How to get that fixed? It's not NM's bits do that - what it doing it?
thanks, L.
There is nothing specific to oVirt in this. You can try searching the net for other guides about how to move a NIC out of a bridge in Linux. If you do this very carefully, you might manage to do this from remote, but I'd personally not try this unless I do have simple access to the machine's console in case I make a mistake.
Good luck and best regards,