On March 14, 2020 11:41:42 PM GMT+02:00, eev...@digitaldatatechs.com wrote:
>I tried a migration on several different vm's. The migratiuon window
>flashes on the screen and immediately errors out saying it cannot get
>the vm ID. (See screen shot)
>Nothing in the logs corresponds to the time I try
Hi,
I'm using a nested environment under kvm with cockpit deployment. I was able to
pass by the Add VM Phase by starting over with another rhv source image. The
NFS shared storage is mapped locally. Everything works fine until the HE is
starting on the shared storage but have no connectivity
Version 4.2.8.2-1.0.9.el7
Per the info near the bottom of
/usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.conf I
should be able to create this file,
/etc/ovirt-engine/engine.conf.d/99-ansible-playbook-timeout.conf
and place in the file these contents,
This is all that should be needed, I've done so on my engine and it works
fine to set the timeout much higher. My guess is that you did not restart
the engine after changing the config.
On Sun, Mar 15, 2020 at 10:44 AM Barrett Richardson
wrote:
> Version 4.2.8.2-1.0.9.el7
>
> Per the info near
Are there any VDSM/server logs as well?
It's hard to tell, as it's not reproducing.
IMHO, the VM was locked before the failed try, and since it's status wasn't
'DOWN' the message came up.
*Regards,*
*Shani Leviim*
On Thu, Mar 12, 2020 at 4:31 PM Gianluca Cecchi
wrote:
> On Thu, Mar 12,
Filed the bug for Ovirt Bugzilla.
Red Hat Bugzilla – Bug 1813711
Eric Evans
Digital Data Services LLC.
304.660.9080
-Original Message-
From: Strahil Nikolov
Sent: Sunday, March 15, 2020 2:59 AM
To: eev...@digitaldatatechs.com; 'Yedidyah Bar David'
Cc: 'users'
Subject: [ovirt-users]
Restarted ovirt-engine service, correct?
Which kind of playbooks?
Il Dom 15 Mar 2020, 14:44 Barrett Richardson ha
scritto:
> Version 4.2.8.2-1.0.9.el7
>
> Per the info near the bottom of
> /usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.conf I should be
> able to create this file,
>
Its looks like key SSHInactivityHardTimeoutSeconds was the source of
my grief.
On 3/15/2020 at 10:14 AM, "Jayme" wrote:This is all that should be
needed, I've done so on my engine and it works fine to set the timeout
much higher. My guess is that you did not restart the engine after
changing the
Hi,
Move should work.
You can backup the disk before migration just to feel safe :)
On Fri, Mar 13, 2020 at 7:28 AM wrote:
> Hi All,
>
> What would be the easiest way to migrate my hosted engine disk from one
> storage domain, to another? I see that I can click on the disk, and select
> move,
Yes, restarted ovirt-engine service. Rebooted even. I'm trying the
Reinstall operation on a new host I'm trying to add to a cluster.
Compute --> Hosts --> olvmHost1 and the tabs are
[Edit][Remove][Management][Installation][Host Console]. Installation
has a pull down menu with options
Tried several migrations and found this in the engine.log:
2020-03-15 13:12:50,760-04 WARN [org.ovirt.engine.core.bll.SearchQuery]
(default task-57) [c0ef4cd1-0391-4741-a345-62b567ed30bf]
ResourceManager::searchBusinessObjects - Invalid search text - ''VMs : id=''
2020-03-15 13:13:19,129-04
11 matches
Mail list logo
