On Mon, Dec 28, 2015 at 3:48 PM, Stefano Danzi <s.da...@hawai.it> wrote: > Problem solved!!! > > The file hosted-engine.conf had a wrong fqdn. > I don't think that this happened during upgrade... mybe thay my colleague > did something of wrong...
Thanks for the report :-) > > > Il 20/12/2015 14.52, Stefano Danzi ha scritto: > > Network problems was solved after changing Bond mode (and it's strange. I > have to investigate around qemu-kvm, cento 7.2 and switch firmware ), but > broker problem still exist. If I turn on the host, ha agent start engine > vm. When engine VM is up, broker strats to send email. Now I haven't here > detailed logs. > > > -------- Messaggio originale -------- > Da: Yedidyah Bar David <d...@redhat.com> > Data: 20/12/2015 11:20 (GMT+01:00) > A: Stefano Danzi <s.da...@hawai.it>, Dan Kenigsberg <dan...@redhat.com> > Cc: users <users@ovirt.org> > Oggetto: Re: [ovirt-users] Network instability after upgrade 3.6.0 -> 3.6.1 > > On Fri, Dec 18, 2015 at 5:31 PM, Stefano Danzi <s.da...@hawai.it> wrote: >> I found this in vdsm.log and I think that could be the problem: >> >> Thread-3771::ERROR::2015-12-18 >> >> 16:18:58,597::brokerlink::279::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(_communicate) >> Connection closed: Connection closed >> Thread-3771::ERROR::2015-12-18 16:18:58,597::API::1847::vds::(_getHaInfo) >> failed to retrieve Hosted Engine HA info >> Traceback (most recent call last): >> File "/usr/share/vdsm/API.py", line 1827, in _getHaInfo >> stats = instance.get_all_stats() >> File >> >> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py", >> line 103, in get_all_stats >> self._configure_broker_conn(broker) >> File >> >> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py", >> line 180, in _configure_broker_conn >> dom_type=dom_type) >> File >> >> "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", >> line 176, in set_storage_domain >> .format(sd_type, options, e)) >> RequestError: Failed to set storage domain FilesystemBackend, options >> {'dom_type': 'nfs3', 'sd_uuid': '46f55a31-f35f-465c-b3e2-df45c05e06a7'}: >> Connection closed > > My guess is that this is a consequence of your networking problems. > > Adding Dan. > >> >> >> Il 17/12/2015 18.51, Stefano Danzi ha scritto: >>> >>> I partially solve the problem. >>> >>> My host machine has 2 network interfaces with a bond. The bond was >>> configured with mode=4 (802.3ad) and switch was configured in the same >>> way. >>> If I remove one network cable the network become stable. With both cables >>> attached the network is instable. >>> >>> I removed the link aggregation configuration from switch and change the >>> bond in mode=2 (balance-xor). Now the network are stable. >>> The strange thing is that previous configuration worked fine for one >>> year... since the last upgrade. >>> >>> Now ha-agent don't reboot the hosted-engine anymore, but I receive two >>> emails from brocker evere 2/5 minutes. >>> First a mail with "ovirt-hosted-engine state transition >>> StartState-ReinitializeFSM" and after "ovirt-hosted-engine state >>> transition >>> ReinitializeFSM-EngineStarting" >>> >>> >>> Il 17/12/2015 10.51, Stefano Danzi ha scritto: >>>> >>>> Hello, >>>> I have one testing host (only one host) with self hosted engine and 2 VM >>>> (one linux and one windows). >>>> >>>> After upgrade ovirt from 3.6.0 to 3.6.1 the network connection works >>>> discontinuously. >>>> Every 10 minutes HA agent restart hosted engine VM because result down. >>>> But the machine is UP, >>>> only the network stop to work for some minutes. >>>> I activate global maintenace mode to prevent engine reboot. If I ssh to >>>> the hosted engine sometimes >>>> the connection work and sometimes no. Using VNC connection to engine I >>>> see that sometime VM reach external network >>>> and sometimes no. >>>> If I do a tcpdump on phisical ethernet interface I don't see any packet >>>> when network on vm don't work. >>>> >>>> Same thing happens fo others two VM. >>>> >>>> Before the upgrade I never had network problems. >>>> _______________________________________________ >>>> Users mailing list >>>> Users@ovirt.org >>>> http://lists.ovirt.org/mailman/listinfo/users >>>> >>> >>> _______________________________________________ >>> Users mailing list >>> Users@ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/users >> >> _______________________________________________ >> Users mailing list >> Users@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users > > > > -- > Didi > > > _______________________________________________ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > -- Didi _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users