Bug 1388778 - Do not reconnect during setupNetworks
Summary: Do not reconnect during setupNetworks
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm-jsonrpc-java
Classification: oVirt
Component: Core
Version: 1.2.6
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ovirt-4.1.0-alpha
: ---
Assignee: Piotr Kliczewski
QA Contact: Jiri Belka
URL:
Whiteboard:
: 1277988 1388364 1399236 (view as bug list)
Depends On:
Blocks: 1389984
TreeView+ depends on / blocked
 
Reported: 2016-10-26 07:54 UTC by Piotr Kliczewski
Modified: 2020-06-11 13:03 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1389984 (view as bug list)
Environment:
Last Closed: 2017-02-15 15:07:42 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.1+
rule-engine: blocker+
mgoldboi: planning_ack+
oourfali: devel_ack+
pstehlik: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 65653 0 ovirt-4.0 NEW do not reconnect to policy reset 2016-10-26 07:57:24 UTC
oVirt gerrit 65697 0 ovirt-engine-4.0 NEW do not reconnect to policy reset 2016-10-26 08:00:13 UTC
oVirt gerrit 65847 0 ovirt-engine-4.0.5 NEW do not reconnect to policy reset 2016-10-28 14:43:20 UTC
oVirt gerrit 66700 0 ovirt-3.6 MERGED do not reconnect to policy reset 2016-11-15 08:00:32 UTC
oVirt gerrit 66701 0 ovirt-engine-3.6 MERGED do not reconnect to policy reset 2016-11-15 15:03:29 UTC

Description Piotr Kliczewski 2016-10-26 07:54:35 UTC 
The engine should not break physical connection before and after setupNetworks is called.
Comment 1 Red Hat Bugzilla Rules Engine 2016-10-26 07:56:29 UTC 
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.
Comment 2 Red Hat Bugzilla Rules Engine 2016-10-26 07:56:29 UTC 
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Comment 3 Yaniv Kaul 2016-10-30 09:24:25 UTC 
*** Bug 1388364 has been marked as a duplicate of this bug. ***
Comment 4 Yaniv Kaul 2016-10-30 09:25:36 UTC 
QE - please be sure to test the scenario @ bug 1388364 when verifying this bug.
(Note that in ovirt-system-tests which failed on this issue, this seems to be OK now).
Comment 6 Oved Ourfali 2016-11-27 12:13:27 UTC 
*** Bug 1277988 has been marked as a duplicate of this bug. ***
Comment 7 Oved Ourfali 2016-11-29 08:05:20 UTC 
*** Bug 1399236 has been marked as a duplicate of this bug. ***
Comment 8 Jiri Belka 2016-12-01 14:37:45 UTC 
Is this related?

~~~
...
2016-12-01 15:19:57,433 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (ajp-/127.0.0.1:8702-3) [422aed37] Command 'PollVDSCommand(HostName = slot-5d.example.com, VdsIdVDSCommandParametersBase:{runAsync='true', hostId='642224e9-1af0-4ff2-a627-f8ec0de03fcf'})' execution failed: VDSGenericException: VDSNetworkException: Timeout during xml-rpc call
2016-12-01 15:19:57,433 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (ajp-/127.0.0.1:8702-3) [422aed37] Timeout waiting for VDSM response: Internal timeout occured
2016-12-01 15:19:57,443 ERROR [org.ovirt.vdsm.jsonrpc.client.JsonRpcClient] (ResponseWorker) [] Not able to update response for "d30ac2e6-3cdf-49d9-bdbd-37239922d212"
...
~~~

If so, this is vdsm-jsonrpc-java-1.1.16-1.el6ev.noarch (3.6.10-1).
Comment 9 Piotr Kliczewski 2016-12-01 15:08:43 UTC 
Jiri,

No it is expected from time to time.
Comment 10 Sandro Bonazzola 2016-12-12 14:03:28 UTC 
The fix for this issue should be included in oVirt 4.1.0 beta 1 released on December 1st. If not included please move back to modified.
Comment 11 Jiri Belka 2016-12-16 09:55:41 UTC 
ok, vdsm-jsonrpc-java-1.3.5-1.20161209104906.gitabdea80.el7.centos.noarch & ovirt-engine-backend-4.1.0-0.2.master.20161213231004.gitfdf720a.el7.centos.noarch

added centos 7 host successfully.
Note You need to log in before you can comment on or make changes to this bug.