Bug 1465839

Summary: Storage pool upgrade does not cause each synced storage domain to refresh its metadata devices
Product: [oVirt] ovirt-engine Reporter: Idan Shaby <ishaby>
Component: Backend.CoreAssignee: Idan Shaby <ishaby>
Status: CLOSED CURRENTRELEASE QA Contact: Raz Tamir <ratamir>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.1.3.3CC: amureini, bugs, ratamir, stirabos
Target Milestone: ovirt-4.1.4Flags: rule-engine: ovirt-4.1+
Target Release: 4.1.4.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-07-28 14:21:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Idan Shaby 2017-06-28 10:44:18 UTC 
Description of problem:
When upgrading the storage pool from version <= 4.0 to >= 4.1, active storage domains are synchronized. As a part of each such process, the engine should try to refresh the storage domain's metadata devices.
Instead of doing that, the refresh process is skipped and logs the following message: "vds id wasn't passed to the command, skipping metadata devices refresh".

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

How reproducible:
100%

Steps to Reproduce:
1. Have an active block domain in a <= 4.0 dc.
2. Upgrade the dc to version >= 4.1.
3. Refer to the info log "vds id wasn't passed to the command, skipping metadata devices refresh".

Actual results:
Metadata devices refresh is skipped.

Expected results:
Metadata devices refresh should not be skipped.

Additional info:
If not skipped, the metadata devices refresh process should call HSMGetStorageDomainInfo.
Comment 1 Raz Tamir 2017-07-16 14:49:51 UTC 
Verified on rhevm-4.1.4.1-0.1.el7 .
Followed the steps to reproduce