Thank you Eyal,For reference - one of the VM's in question is named connect-job-15 and it's disk is called connect-job-15-root.The disks were migrated from phl-datastore (Data Master / NFS / V3) to phl-tevestore-01 (Data / NFS / V3)Best regards,***Mark SteeleCIO / VP Technical Operations | TelVue CorporationTelVue - We Share Your Vision16000 Horizon Way, Suite 100 | Mt. Laurel, NJ 08054On Wed, Dec 13, 2017 at 2:43 AM, Eyal Shenitzky <eshenitz@redhat.com> wrote:Hi Mark,Can you please send the engine log and the VDSM log.This will help us to make a deeper investigation on the scenario that you described.Thanks.On Tue, Dec 12, 2017 at 11:28 PM, Mark Steele <msteele@telvue.com> wrote:______________________________Hello,We have begun migrating VM boot disks from one Storage domain to another. Both the storage domains are NFS and both are V3. The Ovirt instance is oVirt Engine Version: 3.5.0.1-1.el6I am shutting down the VM's prior to migration (not a live migration). When the disks complete their move, I start the VM back up on the original host. The hosts are all running either Ubuntu 14.04 LTS or 16.04 LTSI have experienced the following two issues:- when the VM's come back up, they are not mounting an external NFS mount that is defined in /etc/fstab. The mount can be reinstated manually and survives subsequent reboots - but every VM that has an external NFS mount has this issue after migration- VM's that have a docker instance running no longer respond to web requests on the web server ports that the docker instance is running.Any thoughts on why this would happen would be greatly appreciated.Best regards,***Mark SteeleCIO / VP Technical Operations | TelVue CorporationTelVue - We Share Your Vision_________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--Regards,Eyal Shenitzky