Sure that ovirt is not directly concerned but this has been done
following the foreman integration feature. So a warning doing this in a
fc environnement could be very preventive.
My question was rather : now is there a possibility to recover this
disk? After all, it is only a LVM disk with one
Anaconda and Kickstart are dangerous in FC environments and have been known
to wipe all kinds of data if zoning wasn't properly done prior to os
deployment to new hosts.
Nothing to do with oVirt, it's a common mistake people make at least once
before they step on this specific rake.
On Jun 21, 201
In a traditional installation of an ovirt host, it seems that
provisionning the OS is the first step before talking about vdsm. I
didn't go further, the problem is that this host saw the production LUN
and the kickstart took all the lun into the same VG with a XFS format.
Yes it is an error fro
Let me get this straight:
You added a new host and instead of letting VDSM manage the VM storage you
added it manually, completely independent from oVirt, during an unattended
installation of the host OS? In a production environment?
Why?
-Ursprüngliche Nachricht-
> Von:Nathanaël Blan
On 18/06/15 17:56, Hans-Joachim wrote:
> Hello,
>
> I'm playing around with the optimizer. For a full CentOS 6 oVIRT 3.5.3
> cluster, I've installed a CentOS7 ovirt-optimizer machine as described in
> "Trying out oVirt's Probabilistic Optimizer".
>
> All works fine... the only thing is, I can't
- Original Message -
> From: "Юрий Полторацкий"
> To: "Alon Bar-Lev"
> Cc: users@ovirt.org
> Sent: Thursday, June 18, 2015 4:05:18 PM
> Subject: Re: [ovirt-users] Error while executing action: Cannot add Host.
> Host with the same UUID already exists.
>
> Hi,
>
> I have resolved this
6 matches
Mail list logo
