On Fri, Nov 9, 2018 at 2:19 PM Martin Sivak <msivak@redhat.com> wrote:

Hi,

> It completed without errors and the hosted_engine storage domain and the
> HostedEngine inside it were already visible, without the former dependency
> to create a data domain

Glad it works for you.

This is indeed one of the few small improvements in the new deployment
procedure :) We do not recommend using the old procedure anymore
unless there is something special that does not work there. In other
words, try ansible first from now on.

Exactly: the "vintage" procedure is deprecated and we are also going to remove it in 4.3.

Please notice that now, in addition to the interactive hosted-engine-setup (from CLI and from cockpit GUI), we also have a pure ansible role that can be executed by itself or combined with other ansible roles for automated deployments or to create complex and richer environment with a single ansible playbook.

The project is here:

https://github.com/oVirt/ovirt-ansible-hosted-engine-setup

while its artifacts are distributed as rpms or via ansible galaxy.

Best regards

--
Martin Sivak
HE ex-maintainer :)

On Fri, Nov 9, 2018 at 1:56 PM, Gianluca Cecchi
<gianluca.cecchi@gmail.com> wrote:
>
> On Fri, Nov 9, 2018 at 11:28 AM Simone Tiraboschi <stirabos@redhat.com>
> wrote:
>>
>>
>>
>> On Fri, Nov 9, 2018 at 12:45 AM Gianluca Cecchi
>> <gianluca.cecchi@gmail.com> wrote:
>>>
>>> Hello,
>>> I'm configuring a nested self hosted engine environment with 4.2.7 and
>>> CentOS 7.5.
>>> Domain type is NFS.
>>> I deployed with
>>>
>>> hosted-engine --deploy --noansible
>>>
>>> All went apparently good but after creating the master storage domain I
>>> see that the hosted engine domain is not automatically imported
>>> At the moment I have only one host.
>>>
>>> ovirt-ha-agent status gives every 10 seconds:
>>> Nov 09 00:36:30 ovirtdemo01.localdomain.local ovirt-ha-agent[18407]:
>>> ovirt-ha-agent
>>> ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm ERROR
>>> Unable to identify the OVF_STORE volume, falling back to initial vm.conf.
>>> Please ensure you already added your first data domain for regular VMs
>>>
>>> In engine.log I see every 15 seconds a dumpxml output ad the message:
>>>
>>> 2018-11-09 00:31:52,822+01 WARN
>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder]
>>> (EE-ManagedThreadFactory-engineScheduled-Thread-52) [7fcce3cb] null
>>> architecture type, replacing with x86_64, VM [HostedEngine]
>>>
>>> see full below.
>>>
>>> Any hint?
>>>
>>
>> Hi Gianluca,
>> unfortunately it's a known regression: it's currently tracked here
>> https://bugzilla.redhat.com/1639604
>>
>> In the mean time I'd suggest to use the new ansible flow witch is not
>> affected by this issue or deploy with an engine-appliance shipped before
>> 4.2.5 completing the upgrade on engine side only when everything is there as
>> expected.
>
>
> Thanks Simone,
> I scratched and reinstalled using the 4.2. appliance and the default option
> (with ansible) executing the command:
>
> hosted-engine --deploy
>

> Gianluca
>
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-leave@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/N6XCZ3TZPCYVC4B4554AKQCJ25BE764I/
>