Bug 1383860

Summary: sos vdsm plugin does not capture current information
Product: Red Hat Enterprise Linux 7 Reporter: Marcus West <mwest>
Component: sosAssignee: Pavel Moravec <pmoravec>
Status: CLOSED NOTABUG QA Contact: BaseOS QE - Apps <qe-baseos-apps>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.4CC: agk, bmr, gavin, gveitmic, plambri, sbradley
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-12 09:08:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Marcus West 2016-10-12 01:04:30 UTC 
## Description of problem:

lvm no longer seems to report current information (lvmetad?)

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

rhv-h4.0 (rhvh-4.0-0.20160919.0)
vdsm-4.18.13-1.el7ev.x86_64
sos-3.2-35.el7_2.3.noarch

## How reproducible:

Always

## Steps to Reproduce:

1. check lvs output on SPM
2. create a new disk for a VM
3. check lvm output on SPM again

## Actual results:

It's there, but you can't see it (lvm commands).   Once 'pvscan --cache' is run, then the new lv can be 'seen'

## Expected results:

While this behaviour might be fine, we would at least like the vdsm plugin (sos) to run 'pvscan --cache' before collecting information.  There's a lot of information in this output (lvm size, tags, etc) that we can't easily get anywhere else, and it's critical for provide support for customers.

Asking customers to run 'pvscan --cache' on hosts before running LogCollector would not be acceptable.  

## Additional info: