Thank you very much, i've been searching for this for so long.
--
Respectfully
Mahdi A. Mahdi
From: users-boun...@ovirt.org on behalf of Abi
Askushi
Sent: Saturday, May 20, 2017 4:14:46 PM
To: users
Subject: [ovirt-users] oVirt Power Management with Cisco UCS
Hi,
Can you check if you can mount manually from the DC1 host ?
You can use vdsm/contrib/nfs-check.py .
See also [1]
Regards,
Fred
[1]
http://www.ovirt.org/documentation/how-to/troubleshooting/troubleshooting-nfs-storage-issues/
On Sat, May 20, 2017 at 3:16 PM, shubham dubey wrote:
> I have
On Fri, May 19, 2017 at 06:28:36AM +0300, Leni Kadali Mutungi wrote:
> I'd like the input of the Debian Virtualization Team on the messages
> below. When replying, cc the oVirt team
>
> -- Forwarded message --
> From: Yedidyah Bar David
> Date: Tue, 16 May 2017 09:51:24 +0300
> S
That works, thank you !
Regards,
-
Guy Chen, RHV
Performance
O: +972.9.7692152M: +972.52.8545202
guc...@redhat.com
- Original Message -
> From: "Ondra Machacek"
> To: "Guy Chen"
> Cc: "users"
> Sent: Friday, May 19, 2017 9:22:30 AM
> Subject: Re: [
Done. Thanks!
On May 20, 2017 10:31 AM, "Arik Hadas" wrote:
>
>
> On Fri, May 19, 2017 at 9:42 PM, Joel Diaz wrote:
>
>> Arik,
>>
>> After adding the snapshot repo, and updating the engine, I now see the
>> seal option.
>>
>
> Great. Note that you probably need to update the hosts with the snap
There was a bug filed about a very similar problem when using Cockpit:
https://bugzilla.redhat.com/show_bug.cgi?id=1421249
This looks like a problem with ovirt-hosted-engine-setup not accepting your
response. Can you attachs logs from /var/log/ovirt-hosted-engine-setup ?
As a workaround, you can
Thanks for reply, I am not sure about how to mount the storage domain
manually.
But I have run the nfs-check and it gives no error.
One more thing I want to add is there are another sd also on the same host
which are connected to another dc ,so is this can be a problem in anyway?
On Sun, May 2
On 5/19/17, Juan Hernández wrote:
> Did that restart of the docker daemon resolve the problem?
>
> As far as I can tell that 'RUN sed' instruction that failed is correct.
> I just re-checked it in my environment and it works correctly. Looks
> more like a resources issue or a bug in docker itself.
On 5/22/17, Leni Kadali Mutungi wrote:
On 5/19/17, Juan Hernández wrote:
> On 05/19/2017 05:20 AM, Leni Kadali Mutungi wrote:
>> Running `make build` went fine until I saw this error:
>>
>> Step 26/34 : RUN sed -i 's/multipathd.service //g'
>> /usr/lib/systemd/system/vdsmd.service
>> ---> Runnin
Can you share the Vdsm log from the host that fails to mount ?
On Sun, May 21, 2017 at 10:00 PM, shubham dubey wrote:
> Thanks for reply, I am not sure about how to mount the storage domain
> manually.
> But I have run the nfs-check and it gives no error.
>
> One more thing I want to add is ther
On 05/18/2017 04:53 PM, cmc wrote:
> I have to shut the VM down to stop it trying to repeatedly trying to
> migrate the problematic host (always the same one). If I take it out
> of maintenance, it will move the VMs back to balance (as per policy),
> so this is rather inconvenient. It took leaving
11 matches
Mail list logo