[ovirt-users] Re: cleanup does not cleanup

[Yedidyah Bar David]

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.

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,
--
Didi
_______________________________________________
Users mailing list -- ***@ovirt.org
To unsubscribe send an email to users-***@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/***@ovi

[Ales Musil]

Post by Yedidyah Bar David

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_.
https://gerrit.ovirt.org/c/ovirt-hosted-engine-setup/+/112336 .
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.
- 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?

Hello,

this is done by vdsm persistence. There are two options that are possible
and
pretty safe.
1) Removing the bridge manually and disabling automatic start of vdsm.
2) Remove the bridge via vdsm and save network configuration (vdsm-client
is executed on the host):

# cat mgmt_remove.json
{
"networks": {
"ovirtmgmt": {
"remove": true
}
},
"options": {
"commitOnSuccess": true,
"connectivityCheck": false
},
"bondings": {}
}
# vdsm-client -f mgmt_remove.json Host setupNetworks

Let us know how it went.

Thanks,
Ales

thanks, L.

Post by Yedidyah Bar David
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,

_______________________________________________
Privacy Statement: https://www.ovirt.org/privacy-policy.html
https://www.ovirt.org/community/about/community-guidelines/