Bug 981948

Summary: [RFE] Consider to provide a vdsm-machine-clean-up utility to avoid undesirable behaviour after vdsm installation.
Product: Red Hat Enterprise Virtualization Manager Reporter: Tareq Alayan <talayan>
Component: RFEsAssignee: Andrew Cathrow <acathrow>
Status: CLOSED WONTFIX QA Contact: yeylon <yeylon>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.3.0CC: acathrow, bazulay, bdagan, iheim, lpeer, pprakash, rbalakri, srevivo
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-22 09:35:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tareq Alayan 2013-07-07 09:05:46 UTC
Description of problem:
in 3.3 the vdsm-host is being added to the engine without rebooting after the installation is done.
This behaviour introduces some issues specially when the vdsm-host is being reused by many engines (our qe-env(Jenkins)).

Version-Release number of selected component (if applicable):
3.3

How reproducible:
always

Steps to Reproduce for example:
1. setup an engine and add host
2. create vms in up state
3. add the host to different engine

Actual results:
The host will be added, however:
1. qemu processes will stay up
2. iscsis sessions are still "logged in"
3. old cache under /rhev
4. old vgs
5. need to dmsetup remove all
6. maube running tasks  "vdsClient Tasks clean"
7. we mau need umount iso/export???  
8. restart libvirt 
9. restart rpcbind service 

Expected results:
host is up and clean and devoted to the new engine with no dirty remains

Additional info:

Comment 3 Itamar Heim 2014-06-22 09:35:43 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.