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.
How should this be tested?
(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.
verified on 3.6. master
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.