Hide Forgot
Description of problem: Customer faced issue in the RHEV 3.4 environment. It was noticed when he was not able to add the disk to the vms, it failed with errors as: Operation Add-Disk failed to complete. Add-Disk operation of volume_Disk1 was initiated on VM volume by admin. Also customer was not able to create new vms, or start a powered off vms. The running vms were running fine, but once shutdown they failed to start again. Some messages are as below: VM <vm-name> is down. Exit message: Bad volume specification {.... } Failed to run VM <vm-name> on Host <host-name> Failed to run VM TVMENG (User: admin). Further it was noticed that the soft-link for a storage domain was missing, restoring the same resolved the issue. But we do not know why it was lost. And also when it was lost as there are no events triggered or logged when this could have happened, the issue got noticed when customer failed to add a disk to the vm. The RHEV-M should report such events otherwise we /customer will not get alert about it.
Tal, let's have someone take a look please?
Idan/Amit - once bug 1271771 is solved, what's left to do for this one?
Unfortunately, Since this bug's target release is 4.0.0, I didn't have the chance to get into it yet.
From looking at the logs, it seems like a very similar case to the one in BZ 1271771 (comment 18), although I can't be sure since the logs from the first time vdsm couldn't find the link to the lost domain are missing. Anyway, no matter what the cause for losing the link was, patch 51393 has already solved the links refresh issue, so I guess that it would have solved also this one.
Idan, I tested according to the steps you described in https://bugzilla.redhat.com/show_bug.cgi?id=1271771#c18 and verified 1271771 according to it. Does that mean I can move this one to verified?
Yes, please.
From https://bugzilla.redhat.com/show_bug.cgi?id=1271771#c19 , The symlink under /rhev/data-center was created after connectivity to the storage got resumed and for both, image created successfully once the domain became accessible. Verified using: rhevm-3.6.3.2-0.1.el6.noarch vdsm-4.17.21-0.el7ev.noarch
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/RHEA-2016-0376.html