On Thu, Jul 28, 2016 at 6:44 PM, Kenneth Bingham wrote:
> Do you know of a way to force vdsmd to forget what it knows about the
> network configuration on the hypervisor host? If I synchronize or make any
> change through the engine the host drops off the network because of an
> invalid configuration pushed by some component of oVirt which creates bond1
> with BRIDGE=ovirtmgmt when the bridge should be assigned to bond1.$vid If I
> manually edit the ifcfg files or make changes with the ip command I can
> restore network connectivity, but can not make any changes in engine. It's
> not clear how to recover from this situation without reinstalling the OS.
>
> I've concluded that I should have manually configured the VLAN sub
> interface only before deploying hosted engine which activates vdsmd, then
> configured bonds and VLANs through engine. I believe the ovirtmgmt bridge
> became assigned to the bond instead of the VLAN interface because I
> de-selected VLAN tagging in the logical network configuration in engine,
> and I think most of the problems I'm having are due to my needing to
> manually edit the configuration files written by VDSM in order to bring the
> host back on the network so that it can be managed by engine.
>
It is a bit unclear how the host has been initially setup and what have you
changed on Engine later on to cause this.
VDSM will try to fallback to the previous working network configuration if
a setup command causes a connectivity failure between the host and Engine.
VDSM uses ifcfg files and configuration files to persist its configuration,
but these should be relevant only on boot.
I guess you could uninstall everything and start over.
Alternatively, please provide the following info to try and understand what
is going on at your setup:
- Engine networking config description.
- vdsm and supervdsm logs.
- The files under /var/lib/vdsm/persistence/netconf and /run/vdsm/netconf.
- Output of the command: vdsClient -s 0 getVdsCaps
- Output of the command: ip addr
> # node 4.0.1
> # yum list installed |grep ovirt
> cockpit-ovirt-dashboard.noarch 0.10.5-1.0.0.el7.centos
> installed
> libgovirt.x86_64 0.3.3-1.el7_2.1
> installed
> ovirt-engine-appliance.noarch 4.0-20160718.1.el7.centos
> @ovirt-4.0
> ovirt-engine-sdk-python.noarch 3.6.7.0-1.el7.centos
> installed
> ovirt-host-deploy.noarch 1.5.1-1.el7.centos
> installed
> ovirt-hosted-engine-ha.noarch 2.0.1-1.el7.centos
> installed
> ovirt-hosted-engine-setup.noarch 2.0.1-1.el7.centos
> installed
> ovirt-imageio-common.noarch
> 0.3.0-0.201606191345.git9f3d6d4.el7.centos
> ovirt-imageio-daemon.noarch
> 0.3.0-0.201606191345.git9f3d6d4.el7.centos
> ovirt-node-ng-image-update-placeholder.noarch
> ovirt-release-host-node.noarch 4.0.1-1.el7
> installed
> ovirt-release40-pre.noarch 4.0.1-1
> installed
> ovirt-setup-lib.noarch 1.0.2-1.el7.centos
> installed
> ovirt-vmconsole.noarch 1.0.3-1.el7.centos
> installed
> ovirt-vmconsole-host.noarch1.0.3-1.el7.centos
> installed
>
> # hosted engine appliance
> # yum list installed|grep ovirt
> ebay-cors-filter.noarch 1.0.1-3.el7
> @centos-ovirt40-candidate
> libtomcrypt.x86_64 1.17-23.el7
> @ovirt-4.0-epel
> libtommath.x86_64 0.42.0-4.el7
> @ovirt-4.0-epel
> novnc.noarch0.5.1-2.el7
> @centos-ovirt40-candidate
> otopi.noarch1.5.1-1.el7.centos
> @ovirt-4.0
> otopi-java.noarch 1.5.1-1.el7.centos
> @ovirt-4.0
> ovirt-engine.noarch 4.0.1.1-1.el7.centos
> @ovirt-4.0
> ovirt-engine-backend.noarch 4.0.1.1-1.el7.centos
> @ovirt-4.0
> ovirt-engine-cli.noarch 3.6.8.0-1.el7.centos
> @ovirt-4.0
> ovirt-engine-dashboard.noarch 1.0.0-0.2.20160610git5d210ea.el7.centos
>
> @ovirt-4.0
> ovirt-engine-dbscripts.noarch 4.0.1.1-1.el7.centos
> @ovirt-4.0
> ovirt-engine-dwh.noarch 4.0.1-1.el7.centos
> @ovirt-4.0
> ovirt-engine-dwh-setup.noarch 4.0.1-1.el7.centos
> @ovirt-4.0
> ovirt-engine-extension-aaa-jdbc.noarch
> 1.1.0-1.el7
> @ovirt-4.0
> ovirt-engine-extensions-api-impl.noarch
> 4.0.1.1-1.el7.centos
> @ovirt-4.0
> ovirt-engine-lib.noarch 4.0.1.1-1.el7.centos
> @ovirt-4.0
> ovirt-engine-restapi.noarch 4.0.1.1-1.el7.centos
> @ovirt-4.0
> ovirt-engine-sdk-python.noarch 3.6.7.0-1.el7.centos
> @ovirt-4.0
> ovirt-engine-setup.noarch 4.0.1.1-1.el7.centos
> @ovirt-4.0
> ovirt-engine-setup-base.noarch 4.0.1.1-1.el7.centos
> @ovirt-4.0
> ovirt-engine-setup-plugin-ovirt-engine.noarch
> 4.0.1.1-1.el7.centos
> @ovirt-4.0
> ovirt-engine-setup-plugin-ovirt-engine-common.noarch
> 4.0.1.1-1.el7.centos
> @ovirt-4.0
> ovirt-engine-
