Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1324479

Summary: race between SetupNetwork and event-triggered getVdsCaps
Product: [oVirt] vdsm Reporter: Karolína Hajná <khajna>
Component: GeneralAssignee: Alona Kaplan <alkaplan>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: high Docs Contact:
Priority: high    
Version: ---CC: bugs, danken, edwardh, mburman, pstehlik, ylavi
Target Milestone: ovirt-4.0.2Keywords: Regression
Target Release: 4.18.4Flags: rule-engine: ovirt-4.0.z+
rule-engine: blocker+
rule-engine: planning_ack+
danken: devel_ack+
rule-engine: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-12 14:29:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1240719    
Attachments:
Description Flags
vdsm log
none
engine log none

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