<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 5, 2016 at 10:10 AM, Yedidyah Bar David <span dir="ltr">&lt;<a href="mailto:didi@redhat.com" target="_blank">didi@redhat.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><span class="">On Tue, Apr 5, 2016 at 10:03 AM, Yaniv Kaul &lt;<a href="mailto:ykaul@redhat.com">ykaul@redhat.com</a>&gt; wrote:<br>
&gt; Hi,<br>
&gt;<br>
&gt; I&#39;m trying to install self hosted engine in an automated fashion (via<br>
&gt; Ansible).<br>
&gt; This:<br>
&gt; 1. Doesn&#39;t create a pseudo tty (Ansible is not doing that in its SSH)<br>
&gt; 2. Doesn&#39;t use screen<br>
&gt;<br>
&gt; How can I still install hosted-engine? I seem to be failing around the<br>
&gt; initial checks done at [1].<br>
&gt; I&#39;ve tried various hacks (ssh to localhost, use &#39;-T&#39;, run &#39;screen&#39; locally)<br>
&gt; - none seem to have worked well. I&#39;ve noticed the config option, but not<br>
&gt; sure how to use it - OVEHOSTED_CORE/screenProceed<br>
<br>
</span>You can try:<br>
<br>
hosted-engine --deploy<br>
--otopi-environment=&#39;OVEHOSTED_CORE/screenProceed:bool:True&#39;<br></blockquote><div><br></div><div>Still no go, I&#39;m running:</div><div>hosted-engine --deploy --otopi-environment=&#39;OVEHOSTED_CORE/screenProceed=bool:True&#39; --config-append=/tmp/hosted-engine-answer-file.conf</div><div><br></div><div>And getting:</div><div><br></div><div><div>stdout: [ INFO  ] Stage: Initializing</div><div>[ INFO  ] Generating a temporary VNC password.</div><div>[ INFO  ] Stage: Environment setup</div><div>          Configuration files: [&#39;/tmp/hosted-engine-answer-file.conf&#39;]</div><div>          Log file: /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20160406050029-0syzjx.log</div><div>          Version: otopi-1.4.1 (otopi-1.4.1-1.el7.centos)</div><div>[ 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 </div><div>[WARNING] Aborted</div><div>[ INFO  ] Stage: Clean up</div><div>[ INFO  ] Generating answer file &#39;/var/lib/ovirt-hosted-engine-setup/answers/answers-20160406050029.conf&#39;</div><div>[ INFO  ] Stage: Pre-termination</div><div>[ INFO  ] Stage: Termination</div><div>[ ERROR ] Hosted Engine deployment failed: this system is not reliable, please check the issue, fix and redeploy</div><div>          Log file is located at /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20160406050029-0syzjx.log</div></div><div><br></div><div><br></div><div>(While I suspect there&#39;s some way to cause Ansible to create the tty, it causes issues with sftp. While there&#39;s a way to move from sftp to scp, it then fails on copying files for some odd reason... so if there&#39;s a way to overcome this error in ovirt, that&#39;ll be great).</div><div>Y.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<span class=""><br>
&gt;<br>
&gt; TIA,<br>
&gt; Y.<br>
&gt;<br>
&gt; [1]<br>
&gt; <a href="https://github.com/oVirt/ovirt-hosted-engine-setup/blob/e339fa94637df536865b92e4dc9a2075417b6257/src/plugins/ovirt-hosted-engine-setup/core/shell.py#L53" rel="noreferrer" target="_blank">https://github.com/oVirt/ovirt-hosted-engine-setup/blob/e339fa94637df536865b92e4dc9a2075417b6257/src/plugins/ovirt-hosted-engine-setup/core/shell.py#L53</a><br>
&gt;<br>
</span>&gt; _______________________________________________<br>
&gt; Users mailing list<br>
&gt; <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
&gt; <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
&gt;<br>
<span class=""><font color="#888888"><br>
<br>
<br>
--<br>
Didi<br>
</font></span></blockquote></div><br></div></div>