Hi Jorick,
if I understand correctly you had ovirtmgmt over bond and now you’ve tried to
move it to single interface? You mention that everything is gone after
restarting. Restarting of what? What system is running on your hypervisors? Can
you provide supervdsm.log from the affected node?
Jorick, I experienced similar problems when setting up a few different
test clusters using bonds. I found that the vdsm is not setting the bonds
to persist. These are the steps that worked for me to get the host back
online and fix it permanently:
1. Put the host in Maintenance Mode.
2.
Hi,
I had a similar problem with an upgrade from 3.4 to 3.5. My workaround
was:
1. Put the host in maintenance mode
2. Stop vdsmd and supervdsmd service
3. Manually restore the ifcfg network config files
4. Start vdsmd service (which starts supervdsmd), which succeeds once.
5. Go to
After having problems with a bond and the ovirtmgmt interface on 3.5.1,
I skipped bond0 and just added bond1 for gluster and bond2 for internet.
When restarting, I loose all the bonds and I cannot use the Setup Host
networks anymore:
In the engine log, I see the following:
2015-02-10
4 matches
Mail list logo
