Description of problem:
Is possible to deactive a master domain while other domains (tested for export domain and second data domains) are in preparing_for_maintenance. Both operation succeed, but the export domain is in status "preparing_for_maintenance", so maybe should be allow but the status must be updated properly.
Version-Release number of selected component (if applicable):
ovirt-engine-3.5.0-0.0.master.20140804172041. (ovirt RC1)
Steps to Reproduce:
1. Have a DC with a master domain (NFS) and a export domain active
2. Deactivate export domain
3. While the export domain is being deactivated (status is prepare_for_maintenance") try to deactivate the master domain.
Master domain is deactivated, and the export domain is in "preparing_for_maintenance" permanently, vdsm is running
updateState) Task=`e61366a7-099c-4d66-afd6-6feb2654882c`::moving from state init -> state preparing
all the time.
Seems the problem is the status is not updated in the db.
I expect to master domain to not be deactivated until the export domain is too, or at least it will set the proper status for the export domain.
Checking the vdsm logs there's an error umounting the master domain /usr/share/vdsm/storage/mount.py (tough the operation succeeded, master domain is umounted and on status maintenance).
(In reply to Carlos Mestre González from comment #0)
> Additional info:
> Checking the vdsm logs there's an error umounting the master domain
> /usr/share/vdsm/storage/mount.py (tough the operation succeeded, master
> domain is umounted and on status maintenance).
Forget about this, everything seems fine in the log, the only problem is the status for the export domain is never changed to maintenance.
Carlos, can you attach engine+vdsm logs please?
(In reply to Allon Mureinik from comment #3)
> Carlos, can you attach engine+vdsm logs please?
Disregard - you beat me to it :-)
I've tried to verified this in vt3.1, and is not working. Same issue that state in the bug description, export_domain is in 'preparing for maintenance' since the umount failed (adding vdsm.log)
Created attachment 937921 [details]
vdsm.log for vt3.1
last 5 minutes can see the error
RHEVM's vt3.1 is older than oVirt's RC2 (and moreover, oVirt bugs should be verified with oVirt versions).
Moving back to ON_QA to verify with the right version.
you are right about rc2 but not that we need to verify ovirt bugs on ovirt, we can and verify on both.
(In reply to Aharon Canan from comment #9)
> but not that we need to verify ovirt bugs on ovirt,
> we can and verify on both.
Of course not.
If it's not part of an oVirt build, it's meaningless to a oVirt users.
easy workaround, we can reactivate the master domain and the export enter maintenance