Description of problem: Some storage operations, e,g, old (legacy) cold merge (DC <= 4.0), break the volume leases, because those operations rename the volumes but not their corresponding leases. Broken leases will prevent performing storage jobs after the environment is upgraded. We want to provide an option (Vdsm API) to detect and fix existing broken leases. This bug is related to bug 1538472. However, while the fix of bug 1538472 does rename leases after renaming volumes, that fix doesn't affect this one as this one is about invalid *existing* leases.
Note that this issue is very old, probably since cold merge was introduced. The issue was discovered in 4.1, since we started to use volume leases for storage operations. Since 4.1 volume leases are not effected by cold merge since are not renaming volumes any more during cold merged.
Thank you Ala! Just one question: are there any plans to automate fixing this by the engine making use of this new vdsm api call? Because otherwise we need a how-to KCS Solution/Article, I can write it.
Hi Germano, For now, there is no plan to add a support in the engine to call this new api. I believe that we will have such support in the future. Suggest to write a KCS Solution/Article for this.
(In reply to Ala Hino from comment #3) > Hi Germano, > > For now, there is no plan to add a support in the engine to call this new > api. > I believe that we will have such support in the future. > > Suggest to write a KCS Solution/Article for this. Hi Ala, Does this look good to you? https://access.redhat.com/solutions/3362171 I tried to add some steps for the user to find out the Storage Domain IDs without going through the DB. Thank you
(In reply to Germano Veit Michel from comment #4) > (In reply to Ala Hino from comment #3) > > Hi Germano, > > > > For now, there is no plan to add a support in the engine to call this new > > api. > > I believe that we will have such support in the future. > > > > Suggest to write a KCS Solution/Article for this. > > Hi Ala, > > Does this look good to you? > https://access.redhat.com/solutions/3362171 Looks very good. > > I tried to add some steps for the user to find out the Storage Domain IDs > without going through the DB. > > Thank you Please note that currently I am checking the option to provide a standalone script, i.e. can be executed without vdsm-client. This may be simpler to execute and maintain. I will update ASAP about the direction we choose to go with.
(In reply to Ala Hino from comment #5) > Please note that currently I am checking the option to provide a standalone > script, i.e. can be executed without vdsm-client. > This may be simpler to execute and maintain. This would be nice. Please raise needinfo on me once we can modify the KCS solution with simpler steps, if possible. Thanks
Hi Ala, What are the steps to reproduce? According to https://bugzilla.redhat.com/show_bug.cgi?id=1538472#c3 The bug is already verified for 4.1. I can verify it using the same steps to 4.2 but from which version of DC? 4.0 / 4.1 ? Thank you
Hi Yosi, Exactly same steps. You have to upgrade from DC 4.0. Broken leases exists only in DC <= 4.0.
Verified using the steps from https://bugzilla.redhat.com/show_bug.cgi?id=1538472#c3. DC upgraded from 4.0 to 4.2. Works fine. Moving to VERIFIED
This bugzilla is included in oVirt 4.2.3 release, published on May 4th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.3 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.