On Fri, Aug 14, 2020, 16:16 Juan Pablo Lorier wrote:
> Hi,
>
> I'm having issues with migration to some hosts. I have a 4 node cluster
> and I tried updating to see if it fixes but it's still failing. The reason
> is nos clear in the engine log.
>
>
> 2020-08-14 09:45:32,322-03 INFO
> [org.ovirt.
On Fri, Aug 14, 2020, 16:50 Bob Franzke via Users wrote:
> OK thanks for the reply. As you can perhaps tell I am a complete noob with
> Ovirt. The fact its working now at all is a complete miracle.
>
> >>> I see 2 approaches on fixing the broken storage domain:
> >>> - log to engine, switch to po
OK thanks for the reply. As you can perhaps tell I am a complete noob with
Ovirt. The fact its working now at all is a complete miracle.
>>> I see 2 approaches on fixing the broken storage domain:
>>> - log to engine, switch to postgresql and start searching in the DB for the
>>> uuid.
I am not
Hi,
I'm having issues with migration to some hosts. I have a 4 node cluster
and I tried updating to see if it fixes but it's still failing. The
reason is nos clear in the engine log.
2020-08-14 09:45:32,322-03 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(def
When oVirt creates a storage domain , it assigns an unique id (in the engine
DB) and a single directory, named as the uuid , is created there.
As you lost the dir, your storage domain is gone but as it's an iso domain - it
shouldn't be critical.
I see 2 approaches on fixing the broken storage d
5 matches
Mail list logo
