Bug 1096215

Summary: [RFE] Get rid of the setStoragePoolDescription calls
Product: Red Hat Enterprise Virtualization Manager Reporter: Federico Simoncelli <fsimonce>
Component: ovirt-engineAssignee: Allon Mureinik <amureini>
Status: CLOSED ERRATA QA Contact: Ori Gofen <ogofen>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.5.0CC: acanan, amureini, danken, dornelas, fsimonce, gklein, iheim, lpeer, lyarwood, mkalinin, rbalakri, Rhev-m-bugs, scohen, yeylon, ylavi
Target Milestone: ovirt-3.6.0-rcKeywords: CodeChange, FutureFeature, Improvement
Target Release: 3.6.0Flags: sherold: Triaged+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
: 1185846 (view as bug list) Environment:
Last Closed: 2016-03-09 20:45:27 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:
Bug Depends On: 1185846    
Bug Blocks:    

Description Federico Simoncelli 2014-05-09 13:20:07 UTC
Description of problem:
On our way to drop the storage pool (on the vdsm side), engine should stop trying to update the storage pool description.

setStoragePoolDescription calls should be dropped, we can decide to either drop them completely or maintain them for old DCs.

Even if this would introduce a change of behavior I vote for dropping them altogether.

Comment 7 Yaniv Lavi 2015-04-02 12:49:56 UTC
How should this be tested?

Comment 8 Allon Mureinik 2015-04-02 15:03:19 UTC
(In reply to Yaniv Dary from comment #7)
> How should this be tested?

Update a DC's name and observe in the logs that no call to setStoragePoolDesceription was made.

Comment 9 Ori Gofen 2015-05-03 12:07:57 UTC
verified on 3.6. master

Comment 11 errata-xmlrpc 2016-03-09 20:45:27 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-0376.html