<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Apr 16, 2018 at 12:18 PM, <span dir="ltr"><<a href="mailto:dhy336@sina.com" target="_blank">dhy336@sina.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><span style="background-color:rgb(242,242,242)">Hi Simone </span></div><div>Thanks, I disble selinux, the issue is work, but has other issue, </div><div>error is:</div><div><br></div><div><div>[ INFO ] Engine is still unreachable</div><div>[ INFO ] Engine is still not reachable, waiting...</div><div>[ INFO ] Engine is still unreachable</div><div>[ ERROR ] Engine is still not reachable</div><div>[ ERROR ] Failed to execute stage 'Closing up': Engine is still not reachable</div><div>[ INFO ] Stage: Clean up</div><div>[ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine-<wbr>setup/answers/answers-<wbr>20180416095044.conf'</div></div><div><br></div><div>when #hosted-engine --deploy I setup static ip, and set ip in /etc/hosts. </div><div>VM`s ip is same with that i set.</div><div><br></div></blockquote><div><br></div><div>Can you please check the status of ovirt-engine service on the engine VM?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div></div><div><br></div><div> </div><div><br></div><div><br></div><div><br></div><div><br></div><div id="m_-3930467395630237708origbody"><div style="background:#f2f2f2">----- 原始邮件 -----<br>发件人：Simone Tiraboschi <<a href="mailto:stirabos@redhat.com" target="_blank">stirabos@redhat.com</a>><br>收件人：<a href="mailto:dhy336@sina.com" target="_blank">dhy336@sina.com</a><br>抄送人：users <<a href="mailto:users@ovirt.org" target="_blank">users@ovirt.org</a>><br>主题：Re: [ovirt-users] hosted-engine --deploy failed<br>日期：2018年04月16日 15点24分<br></div><div><div class="h5"><br><div dir="ltr"><div>2018-04-16 05:50:09,331+0800 DEBUG otopi.plugins.otopi.network.<wbr>firewalld plugin.executeRaw:813 execute: ('/usr/bin/firewall-cmd', '--list-all-zones'), executable='None', cwd='None', env=None</div><div>2018-04-16 14:21:26,331+0800 DEBUG otopi.plugins.otopi.network.<wbr>firewalld plugin.executeRaw:869 execute-result: ('/usr/bin/firewall-cmd', '--list-all-zones'), exception</div><div><br></div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">'firewall-cmd <span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">--list-all-<wbr>zones' got stuck on the engine VM; we had similar issue in the past to SELinux rues.</span></span><br></div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">If you are deploying with a custom cloud-init ISO image with custom script please try disabling SELinux there just for engine-setup execution time.</span></span></div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br></span></span></div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br></span></span></div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">As a general rule I'd suggest to move instead to the new ansible based flow where engine-setup is executed via ansible in a more controllable way.</span></span></div><div><br><div>On Mon, Apr 16, 2018 at 8:44 AM, <span dir="ltr"><<a href="mailto:dhy336@sina.com" target="_blank">dhy336@sina.com</a>></span> wrote:<br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>Hi，</div><div> when I depoy hosted engine by #hosted-engine --deploy</div><div><br></div><div><div> |- [ INFO ] Stage: Transaction setup</div><div> |- [ INFO ] Stopping engine service</div><div> |- [ INFO ] Stopping ovirt-fence-kdump-listener service</div><div> |- [ INFO ] Stopping dwh service</div><div> |- [ INFO ] Stopping Image I/O Proxy service</div><div> |- [ INFO ] Stopping vmconsole-proxy service</div><div> |- [ INFO ] Stopping websocket-proxy service</div><div> |- [ INFO ] Stage: Misc configuration</div><div> [ ERROR ] Engine setup got stuck on the appliance</div><div> [ ERROR ] Failed to execute stage 'Closing up': Engine setup is stalled on the appliance since 1800 seconds ago. Please check its log on the appliance. </div><div> [ INFO ] Stage: Clean up</div><div> [ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine-<wbr>setup/answers/answers-20180416<wbr>062012.conf'</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-s<wbr>etup/ovirt-hosted-engine-setup<wbr>-20180416054143-5p2ilc.log</div><div><br></div><div>engine-setup take a lot time in "Stage: Misc configuration", and finaly failed.</div><div><br></div><div><font face="Arial, Microsoft YaHei, 微软雅黑, 宋体, Malgun Gothic, Meiryo, sans-serif"><span style="font-size:13px;background-color:rgb(249,251,252)">My mail attachment is hosted-engine --deploy log and VM engine-setup log.</span></font></div><div><font face="Arial, Microsoft YaHei, 微软雅黑, 宋体, Malgun Gothic, Meiryo, sans-serif"><span style="font-size:13px;background-color:rgb(249,251,252)"><br></span></font></div><div><span style="font-size:13px;background-color:rgb(249,251,252)"><font face="Arial, Microsoft YaHei, 微软雅黑, 宋体, Malgun Gothic, Meiryo, sans-serif">would you give me some advi</font><font face="幼圆">se? Thanks...</font></span></div><div><br></div><div><br></div></div><div><br></div><br>______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/users</a><br>
<br></blockquote></div><br></div></div>
</div></div></div></blockquote></div><br></div></div>