Bug 1324479 - race between SetupNetwork and event-triggered getVdsCaps
Summary: race between SetupNetwork and event-triggered getVdsCaps
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: General
Version: ---
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.0.2
: 4.18.4
Assignee: Alona Kaplan
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks: 1240719
TreeView+ depends on / blocked
 
Reported: 2016-04-06 12:34 UTC by Karolína Hajná
Modified: 2016-08-12 14:29 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-12 14:29:22 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-4.0.z+
rule-engine: blocker+
rule-engine: planning_ack+
danken: devel_ack+
rule-engine: testing_ack+

Attachments (Terms of Use)
vdsm log (4.84 MB, text/plain)
2016-04-08 06:33 UTC, Karolína Hajná 		no flags Details
engine log (2.38 MB, text/plain)
2016-04-08 06:36 UTC, Karolína Hajná 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 59318 0 master NEW engine: Block GetCaps and SetupNetworks running in parallel 2016-06-22 09:43:45 UTC
oVirt gerrit 60016 0 None None None 2016-07-04 11:46:39 UTC

Description Karolína Hajná 2016-04-06 12:34:21 UTC 
Description of problem:
Non-operational host in engine cannot be put to maintenance mode. When trying to do so, the host will switch back to non-operational after few seconds. 


Version-Release number of selected component (if applicable):
vdsm-4.17.999-879.git565cb2e.el7.centos.noarch

How reproducible:
100%

Steps to Reproduce:
1. Install a host with non-operational status
2. Try to switch the host to maintenance mode
3. Wait few seconds

Actual results:
After a while the host switches from maintenance back to non-operational

Expected results:
Host stays in maintenance
Comment 1 Dan Kenigsberg 2016-04-07 05:46:57 UTC 
would you provide your engine and vdsm logs?

Martin, could it be related to our newly-generated connectivity events?
Comment 2 Martin Mucha 2016-04-07 06:44:59 UTC 
(In reply to Dan Kenigsberg from comment #1)
> would you provide your engine and vdsm logs?
> 
> Martin, could it be related to our newly-generated connectivity events?

HostConnectionRefresher calls GetCapabilities upon vdsm event, which is fired after few secs, after host status is changed. Call GetCapabilities code was reused, so if this is caused by HostConnectionRefresher, we probably had same behavior with manually clicking RefreshCapabilities button.

I'll look at it.
Comment 3 Red Hat Bugzilla Rules Engine 2016-04-07 13:17:21 UTC 
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Comment 4 Karolína Hajná 2016-04-08 06:33:12 UTC 
Created attachment 1145009 [details]
vdsm log
Comment 5 Karolína Hajná 2016-04-08 06:36:43 UTC 
Created attachment 1145010 [details]
engine log
Comment 6 Sandro Bonazzola 2016-05-02 09:55:17 UTC 
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
Comment 8 Yaniv Lavi 2016-05-23 13:16:55 UTC 
oVirt 4.0 beta has been released, moving to RC milestone.
Comment 9 Yaniv Lavi 2016-05-23 13:23:23 UTC 
oVirt 4.0 beta has been released, moving to RC milestone.
Comment 10 Michael Burman 2016-07-24 11:17:57 UTC 
Verified on - vdsm-4.18.8-1.el7ev.x86_64
Note You need to log in before you can comment on or make changes to this bug.