Test using rhevm-3.5.1-0.1.el6ev, vdsm-4.16.12-2.el7ev.x86_64
Maor, please provide doctext for this bug (and the 3.6.0 too, while you're at it).
Hi Allon, I'm having trouble understanding this bug but Maor is on PTO. Please let me know if the doc text is not correct. Kind regards, Julie
(In reply to Julie from comment #4) > Hi Allon, I'm having trouble understanding this bug but Maor is on PTO. > Please let me know if the doc text is not correct. > > Kind regards, > Julie The doctext seems correct, although I wonder if the phrasing could be improved. The underlying issue is that VDSM cannot attach an old storage domain with metadata leftovers (i.e., a storage domain that was not cleanly put to maintenance and disconnected from its old setup) to an uninitialized datacenter. In 3.5.0 (before this fix), we would attempt to attach it, and fail with an ugly exception from VDSM. In 3.5.1 (after this fix), we check the domain before attempting to attach it, and if it has metadata leftovers, a human-readable CanDoAction message that explains the situation and how to rectify is is displayed.
(In reply to Allon Mureinik from comment #5) > (In reply to Julie from comment #4) > > Hi Allon, I'm having trouble understanding this bug but Maor is on PTO. > > Please let me know if the doc text is not correct. > > > > Kind regards, > > Julie > > The doctext seems correct, although I wonder if the phrasing could be > improved. > The underlying issue is that VDSM cannot attach an old storage domain with > metadata leftovers (i.e., a storage domain that was not cleanly put to > maintenance and disconnected from its old setup) to an uninitialized > datacenter. > > In 3.5.0 (before this fix), we would attempt to attach it, and fail with an > ugly exception from VDSM. > > In 3.5.1 (after this fix), we check the domain before attempting to attach > it, and if it has metadata leftovers, a human-readable CanDoAction message > that explains the situation and how to rectify is is displayed. Thanks Allon. I have updated the doc text again. Kind regards, Julie
*** Bug 1212799 has been marked as a duplicate of this bug. ***
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/RHSA-2015-0888.html