Description of problem:

dmeventd thin plugin stops retrying resize of thin pool if there is a failure - to avoid stopping filling system logs with lots of failures and archives.

However when the VG is i.e. extended with a new space, there is currently no mechanism to let know dmeventd there is new chance to 'resize'.

ATM user has to manually at least run 'vgchange --refresh' after i.e. 'vgextend' or even 'lvremove'

So the purpose of BZ is provide some solution here.

As a proposal seems to be a reuse of mechanism used for update of lvmetad,
where before drop of VG lock lvmetad is updated.



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

How reproducible:


Steps to Reproduce:
1. let resize fail because there is no space in vg 
2. add new space
3. resize will not happen anyway

Actual results:


Expected results:


Additional info: