[ovirt-users] Installing self-hosted-engine via SSH, without screen

Yedidyah Bar David didi at redhat.com
Wed Apr 6 12:30:54 UTC 2016


On Wed, Apr 6, 2016 at 3:22 PM, Yaniv Kaul <ykaul at redhat.com> wrote:
>
>
> On Wed, Apr 6, 2016 at 2:22 PM, Simone Tiraboschi <stirabos at redhat.com>
> wrote:
>>
>> On Wed, Apr 6, 2016 at 11:50 AM, Sandro Bonazzola <sbonazzo at redhat.com>
>> wrote:
>> >
>> >
>> > On Wed, Apr 6, 2016 at 11:46 AM, Simone Tiraboschi <stirabos at redhat.com>
>> > wrote:
>> >>
>> >> On Wed, Apr 6, 2016 at 11:28 AM, Yaniv Kaul <ykaul at redhat.com> wrote:
>> >> >
>> >> >
>> >> > On Tue, Apr 5, 2016 at 10:10 AM, Yedidyah Bar David <didi at redhat.com>
>> >> > wrote:
>> >> >>
>> >> >> On Tue, Apr 5, 2016 at 10:03 AM, Yaniv Kaul <ykaul at redhat.com>
>> >> >> wrote:
>> >> >> > Hi,
>> >> >> >
>> >> >> > I'm trying to install self hosted engine in an automated fashion
>> >> >> > (via
>> >> >> > Ansible).
>> >> >> > This:
>> >> >> > 1. Doesn't create a pseudo tty (Ansible is not doing that in its
>> >> >> > SSH)
>> >> >> > 2. Doesn't use screen
>> >> >> >
>> >> >> > How can I still install hosted-engine? I seem to be failing around
>> >> >> > the
>> >> >> > initial checks done at [1].
>> >> >> > I've tried various hacks (ssh to localhost, use '-T', run 'screen'
>> >> >> > locally)
>> >> >> > - none seem to have worked well. I've noticed the config option,
>> >> >> > but
>> >> >> > not
>> >> >> > sure how to use it - OVEHOSTED_CORE/screenProceed
>> >> >>
>> >> >> You can try:
>> >> >>
>> >> >> hosted-engine --deploy
>> >> >> --otopi-environment='OVEHOSTED_CORE/screenProceed:bool:True'
>> >> >
>> >> >
>> >> > Still no go, I'm running:
>> >> > hosted-engine --deploy
>> >> > --otopi-environment='OVEHOSTED_CORE/screenProceed=bool:True'
>> >> > --config-append=/tmp/hosted-engine-answer-file.conf
>> >>
>> >> Installing screen and simply running
>> >>  screen hosted-engine --deploy
>> >> --config-append=/tmp/hosted-engine-answer-file.conf
>> >> is not enough?
>> >
>> >
>> > He's using ansible not ssh.
>>
>> Indeed,
>> I mean running
>>  screen hosted-engine --deploy
>> instead of just
>>  hosted-engine --deploy
>> from ansible
>
>
> It didn't. I tried various hacks:
> export TERM=xterm && ...
> screen -T xterm ...
>
> Played around with Ansible configuration...
> None worked.

Perhaps use 'screen -d -m'?

You'll then need other means to know when it finished.

E.g. something like:

screen -S hosted-engine-run -d -m sh -c 'hosted-engine --deploy other
opts'; while screen -list | grep -q hosted-engine-run; do sleep 10;
done

> Y.
>>
>>
>>
>> >>
>> >>
>> >> > And getting:
>> >> >
>> >> > stdout: [ INFO  ] Stage: Initializing
>> >> > [ INFO  ] Generating a temporary VNC password.
>> >> > [ INFO  ] Stage: Environment setup
>> >> >           Configuration files:
>> >> > ['/tmp/hosted-engine-answer-file.conf']
>> >> >           Log file:
>> >> >
>> >> >
>> >> > /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20160406050029-0syzjx.log
>> >> >           Version: otopi-1.4.1 (otopi-1.4.1-1.el7.centos)
>> >> > [ ERROR ] It has been detected that this program is executed through
>> >> > an
>> >> > SSH
>> >> > connection without pseudo-tty allocation. Please run again ssh adding
>> >> > -t
>> >> > option
>> >> > [WARNING] Aborted
>> >> > [ INFO  ] Stage: Clean up
>> >> > [ INFO  ] Generating answer file
>> >> >
>> >> > '/var/lib/ovirt-hosted-engine-setup/answers/answers-20160406050029.conf'
>> >> > [ INFO  ] Stage: Pre-termination
>> >> > [ INFO  ] Stage: Termination
>> >> > [ ERROR ] Hosted Engine deployment failed: this system is not
>> >> > reliable,
>> >> > please check the issue, fix and redeploy
>> >> >           Log file is located at
>> >> >
>> >> >
>> >> > /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20160406050029-0syzjx.log
>> >> >
>> >> >
>> >> > (While I suspect there's some way to cause Ansible to create the tty,
>> >> > it
>> >> > causes issues with sftp. While there's a way to move from sftp to
>> >> > scp,
>> >> > it
>> >> > then fails on copying files for some odd reason... so if there's a
>> >> > way
>> >> > to
>> >> > overcome this error in ovirt, that'll be great).
>> >> > Y.
>> >> >
>> >> >
>> >> >>
>> >> >>
>> >> >> >
>> >> >> > TIA,
>> >> >> > Y.
>> >> >> >
>> >> >> > [1]
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > https://github.com/oVirt/ovirt-hosted-engine-setup/blob/e339fa94637df536865b92e4dc9a2075417b6257/src/plugins/ovirt-hosted-engine-setup/core/shell.py#L53
>> >> >> >
>> >> >> > _______________________________________________
>> >> >> > Users mailing list
>> >> >> > Users at ovirt.org
>> >> >> > http://lists.ovirt.org/mailman/listinfo/users
>> >> >> >
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Didi
>> >> >
>> >> >
>> >> >
>> >> > _______________________________________________
>> >> > Users mailing list
>> >> > Users at ovirt.org
>> >> > http://lists.ovirt.org/mailman/listinfo/users
>> >> >
>> >> _______________________________________________
>> >> Users mailing list
>> >> Users at ovirt.org
>> >> http://lists.ovirt.org/mailman/listinfo/users
>> >
>> >
>> >
>> >
>> > --
>> > Sandro Bonazzola
>> > Better technology. Faster innovation. Powered by community
>> > collaboration.
>> > See how it works at redhat.com
>
>
>
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>



-- 
Didi



More information about the Users mailing list