On Tue, Dec 13, 2016 at 11:05 AM, Koen Vanoppen <vanoppen.koen@gmail.com> wrote:
> Thanks! The answer file I'm using is from 4.0... So, it's kinda strange he
> quits on the Localhost database for DWH.

OK, sorry for not checking the file earlier.

Perhaps you are using for a new setup, an answer file generated by an upgrade?

If so, please use one generated in exactly the same environment it's
intended for.
Otherwise, please provide detailed flow and relevant logs.

Thanks!

> I'll check the otopi option.

OK. Please also share your experience/opinion about this. Thanks.

Best,

>
> Kind regards,
> Koen
>
>
> On Tue, 13 Dec 2016 at 09:47 Yedidyah Bar David <didi@redhat.com> wrote:
>>
>> On Tue, Dec 13, 2016 at 8:36 AM, Koen Vanoppen <vanoppen.koen@gmail.com>
>> wrote:
>> > Dear all,
>> >
>> > I'm currently trying to create a puppet module for setting up ovirt from
>> > scratch.
>> > For the moment I'm stuck with the answer file that hangs on this (and
>> > then
>> > of course stops the installation):
>> >
>> > Notice: /Stage[main]/Bacovirt::Config::Mgmt/Exec[engine-setup]/returns:
>> > --== DATABASE CONFIGURATION ==--
>> > Notice: /Stage[main]/Bacovirt::Config::Mgmt/Exec[engine-setup]/returns:
>> > Notice: /Stage[main]/Bacovirt::Config::Mgmt/Exec[engine-setup]/returns:
>> > Where is the DWH database located? (Local, Remote) [Local]: [ ERROR ]
>> > Failed
>> > to execute stage 'Environment customization': End of file
>> >
>> > My answer file is included as a attachment.
>>
>> Didn't check it, but most likely it was generated by/for a <=3.6
>> engine-setup.
>> In 4.0, the engine now requires dwh, so requires its setup package, which
>> adds this question.
>>
>> Simply run engine-setup manually and compare the generated answer file
>> with yours.
>>
>> You might also want to try the rather-new otopi option to automatically
>> accept defaults - this way, you can provide an answer file with only the
>> things you supply non-default (or required) answers. See also:
>>
>> https://bugzilla.redhat.com/1270719
>>
>> '--accept-defaults' was only merged to 4.1 engine-setup, but the otopi
>> option (see comment 8) is in otopi-1.5, which is included in 4.0.
>>
>> Best,
>> --
>> Didi



--
Didi