hosted-engine --deploy Failed
Dear All: Recently I just make a try to create a Self-Hosted Engine oVirt but unfortunately both two of my box also failed with bad deployment experience, first of all the online documentation is wrong under "oVirt Self-Hosted Engine Guide" section, it says the deployment script "hosted-engine --deploy" will asking for Storage configuration immediately but it is not true any more, also on both of my 2 box one is configured with bond interface and one not but also failed, in order to separate the issue I think better I post the bonded interface one log for all your to Ref. first, the script runs at "TASK [Wait for the host to be up]" for long long time then give me the Error [ ERROR ] fatal: [localhost]: FAILED! => {"ansible_facts": {"ovirt_hosts": []}, "attempts": 120, "changed": false} [ INFO ] TASK [include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [Remove local vm dir] [ INFO ] changed: [localhost] [ INFO ] TASK [Notify the user about a failure] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"} [ ERROR ] [DEPRECATION WARNING]: Using tests as filters is deprecated. Instead of using [ ERROR ] `result|succeeded` instead use `result is succeeded`. This feature will be [ ERROR ] removed in version 2.9. Deprecation warnings can be disabled by setting [ ERROR ] deprecation_warnings=False in ansible.cfg. [ ERROR ] [DEPRECATION WARNING]: Using tests as filters is deprecated. Instead of using [ ERROR ] `result|succeeded` instead use `result is succeeded`. This feature will be [ ERROR ] removed in version 2.9. Deprecation warnings can be disabled by setting [ ERROR ] deprecation_warnings=False in ansible.cfg. [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook [ INFO ] Stage: Clean up [ INFO ] Cleaning temporary resources [ INFO ] TASK [Gathering Facts] [ INFO ] ok: [localhost] [ INFO ] TASK [include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [Remove local vm dir] [ INFO ] ok: [localhost] [ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20180501190540.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Hosted Engine deployment failed: please check the logs for the issue, fix accordingly or re-deploy from scratch. Log file is located at /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20180501184459-4v6ctw.log Attached is the so long LOG.
Hi Paul, I'm sorry to hear that you're having trouble with the hosted engine deployment process. I looked through the log, but wasn't able to find anything to explain why setup failed to bring up the VM. To clarify, did both of your deployment attempts fail at the same place in the process with the same error message? Also, did you use the same storage device for the storage domain in both attempts? Our resident expert is out today, but should be back tomorrow. I've copied him on this message, so he can follow up once he's back if no one else has been able to help before then. As far as the documentation goes, there have been major changes to the deployment process over the last few months and unfortunately, the documentation simply hasn't caught up and for that, I apologize. It should be updated in the near future to reflect the changes that have been made. Best regards, -Phillip Bailey On Tue, May 1, 2018 at 7:43 AM, Paul.LKW <paul.lkw@gmail.com> wrote:
Dear All: Recently I just make a try to create a Self-Hosted Engine oVirt but unfortunately both two of my box also failed with bad deployment experience, first of all the online documentation is wrong under "oVirt Self-Hosted Engine Guide" section, it says the deployment script "hosted-engine --deploy" will asking for Storage configuration immediately but it is not true any more, also on both of my 2 box one is configured with bond interface and one not but also failed, in order to separate the issue I think better I post the bonded interface one log for all your to Ref. first, the script runs at "TASK [Wait for the host to be up]" for long long time then give me the Error
[ ERROR ] fatal: [localhost]: FAILED! => {"ansible_facts": {"ovirt_hosts": []}, "attempts": 120, "changed": false} [ INFO ] TASK [include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [Remove local vm dir] [ INFO ] changed: [localhost] [ INFO ] TASK [Notify the user about a failure] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"} [ ERROR ] [DEPRECATION WARNING]: Using tests as filters is deprecated. Instead of using [ ERROR ] `result|succeeded` instead use `result is succeeded`. This feature will be [ ERROR ] removed in version 2.9. Deprecation warnings can be disabled by setting [ ERROR ] deprecation_warnings=False in ansible.cfg. [ ERROR ] [DEPRECATION WARNING]: Using tests as filters is deprecated. Instead of using [ ERROR ] `result|succeeded` instead use `result is succeeded`. This feature will be [ ERROR ] removed in version 2.9. Deprecation warnings can be disabled by setting [ ERROR ] deprecation_warnings=False in ansible.cfg. [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook [ INFO ] Stage: Clean up [ INFO ] Cleaning temporary resources [ INFO ] TASK [Gathering Facts] [ INFO ] ok: [localhost] [ INFO ] TASK [include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [Remove local vm dir] [ INFO ] ok: [localhost] [ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine- setup/answers/answers-20180501190540.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Hosted Engine deployment failed: please check the logs for the issue, fix accordingly or re-deploy from scratch. Log file is located at /var/log/ovirt-hosted-engine-s etup/ovirt-hosted-engine-setup-20180501184459-4v6ctw.log
Attached is the so long LOG.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
I was having the same issue. I've blown away my logs, but VDSM was failing to start up after attempting to configure vswitch filtering. Have switched to oVirt Node, which seems to be working. On Tue, May 1, 2018, 10:00 Phillip Bailey <phbailey@redhat.com> wrote:
Hi Paul,
I'm sorry to hear that you're having trouble with the hosted engine deployment process. I looked through the log, but wasn't able to find anything to explain why setup failed to bring up the VM. To clarify, did both of your deployment attempts fail at the same place in the process with the same error message? Also, did you use the same storage device for the storage domain in both attempts?
Our resident expert is out today, but should be back tomorrow. I've copied him on this message, so he can follow up once he's back if no one else has been able to help before then.
As far as the documentation goes, there have been major changes to the deployment process over the last few months and unfortunately, the documentation simply hasn't caught up and for that, I apologize. It should be updated in the near future to reflect the changes that have been made.
Best regards,
-Phillip Bailey
On Tue, May 1, 2018 at 7:43 AM, Paul.LKW <paul.lkw@gmail.com> wrote:
Dear All: Recently I just make a try to create a Self-Hosted Engine oVirt but unfortunately both two of my box also failed with bad deployment experience, first of all the online documentation is wrong under "oVirt Self-Hosted Engine Guide" section, it says the deployment script "hosted-engine --deploy" will asking for Storage configuration immediately but it is not true any more, also on both of my 2 box one is configured with bond interface and one not but also failed, in order to separate the issue I think better I post the bonded interface one log for all your to Ref. first, the script runs at "TASK [Wait for the host to be up]" for long long time then give me the Error
[ ERROR ] fatal: [localhost]: FAILED! => {"ansible_facts": {"ovirt_hosts": []}, "attempts": 120, "changed": false} [ INFO ] TASK [include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [Remove local vm dir] [ INFO ] changed: [localhost] [ INFO ] TASK [Notify the user about a failure] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"} [ ERROR ] [DEPRECATION WARNING]: Using tests as filters is deprecated. Instead of using [ ERROR ] `result|succeeded` instead use `result is succeeded`. This feature will be [ ERROR ] removed in version 2.9. Deprecation warnings can be disabled by setting [ ERROR ] deprecation_warnings=False in ansible.cfg. [ ERROR ] [DEPRECATION WARNING]: Using tests as filters is deprecated. Instead of using [ ERROR ] `result|succeeded` instead use `result is succeeded`. This feature will be [ ERROR ] removed in version 2.9. Deprecation warnings can be disabled by setting [ ERROR ] deprecation_warnings=False in ansible.cfg. [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook [ INFO ] Stage: Clean up [ INFO ] Cleaning temporary resources [ INFO ] TASK [Gathering Facts] [ INFO ] ok: [localhost] [ INFO ] TASK [include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [Remove local vm dir] [ INFO ] ok: [localhost] [ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20180501190540.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Hosted Engine deployment failed: please check the logs for the issue, fix accordingly or re-deploy from scratch. Log file is located at /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20180501184459-4v6ctw.log
Attached is the so long LOG.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
This is a multi-part message in MIME format. --------------DF05F08A6421548E64556F4E Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Dear Philip: It is not failed at the same point and I am using the localhost NFS as the Storage currently as for testing purpose. For the bonding interface host it even not going till that point asking to setup Storage but the other does reach that point but still failed at some other point. I will provide another LOG later till this one solved first as it will confusing all other in the mailing list I think, ^_^ Best Regards, Paul.LKW Phillip Bailey 於 1/5/2018 21:59 寫道:
Hi Paul,
I'm sorry to hear that you're having trouble with the hosted engine deployment process. I looked through the log, but wasn't able to find anything to explain why setup failed to bring up the VM. To clarify, did both of your deployment attempts fail at the same place in the process with the same error message? Also, did you use the same storage device for the storage domain in both attempts?
Our resident expert is out today, but should be back tomorrow. I've copied him on this message, so he can follow up once he's back if no one else has been able to help before then.
As far as the documentation goes, there have been major changes to the deployment process over the last few months and unfortunately, the documentation simply hasn't caught up and for that, I apologize. It should be updated in the near future to reflect the changes that have been made.
Best regards,
-Phillip Bailey
On Tue, May 1, 2018 at 7:43 AM, Paul.LKW <paul.lkw@gmail.com <mailto:paul.lkw@gmail.com>> wrote:
Dear All: Recently I just make a try to create a Self-Hosted Engine oVirt but unfortunately both two of my box also failed with bad deployment experience, first of all the online documentation is wrong under "oVirt Self-Hosted Engine Guide" section, it says the deployment script "hosted-engine --deploy" will asking for Storage configuration immediately but it is not true any more, also on both of my 2 box one is configured with bond interface and one not but also failed, in order to separate the issue I think better I post the bonded interface one log for all your to Ref. first, the script runs at "TASK [Wait for the host to be up]" for long long time then give me the Error
[ ERROR ] fatal: [localhost]: FAILED! => {"ansible_facts": {"ovirt_hosts": []}, "attempts": 120, "changed": false} [ INFO ] TASK [include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [Remove local vm dir] [ INFO ] changed: [localhost] [ INFO ] TASK [Notify the user about a failure] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"} [ ERROR ] [DEPRECATION WARNING]: Using tests as filters is deprecated. Instead of using [ ERROR ] `result|succeeded` instead use `result is succeeded`. This feature will be [ ERROR ] removed in version 2.9. Deprecation warnings can be disabled by setting [ ERROR ] deprecation_warnings=False in ansible.cfg. [ ERROR ] [DEPRECATION WARNING]: Using tests as filters is deprecated. Instead of using [ ERROR ] `result|succeeded` instead use `result is succeeded`. This feature will be [ ERROR ] removed in version 2.9. Deprecation warnings can be disabled by setting [ ERROR ] deprecation_warnings=False in ansible.cfg. [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook [ INFO ] Stage: Clean up [ INFO ] Cleaning temporary resources [ INFO ] TASK [Gathering Facts] [ INFO ] ok: [localhost] [ INFO ] TASK [include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [Remove local vm dir] [ INFO ] ok: [localhost] [ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20180501190540.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Hosted Engine deployment failed: please check the logs for the issue, fix accordingly or re-deploy from scratch. Log file is located at /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20180501184459-4v6ctw.log
Attached is the so long LOG.
_______________________________________________ Users mailing list Users@ovirt.org <mailto:Users@ovirt.org> http://lists.ovirt.org/mailman/listinfo/users <http://lists.ovirt.org/mailman/listinfo/users>
--------------DF05F08A6421548E64556F4E Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> <p>Dear Philip:<br> It is not failed at the same point and I am using the localhost NFS as the Storage currently as for testing purpose.<br> For the bonding interface host it even not going till that point asking to setup Storage but the other does reach that point but still failed at some other point.</p> <p>I will provide another LOG later till this one solved first as it will confusing all other in the mailing list I think, ^_^<br> <br> Best Regards,<br> Paul.LKW<br> </p> <br> <div class="moz-cite-prefix">Phillip Bailey 於 1/5/2018 21:59 寫道:<br> </div> <blockquote type="cite" cite="mid:CAAXfETyihp1ZP+yF6Z1U3txuY--aJcFoM9Yt3x9rZO2+kjF1aA@mail.gmail.com"> <div dir="ltr">Hi Paul, <div><br> </div> <div>I'm sorry to hear that you're having trouble with the hosted engine deployment process. I looked through the log, but wasn't able to find anything to explain why setup failed to bring up the VM. To clarify, did both of your deployment attempts fail at the same place in the process with the same error message? Also, did you use the same storage device for the storage domain in both attempts?</div> <div><br> </div> <div>Our resident expert is out today, but should be back tomorrow. I've copied him on this message, so he can follow up once he's back if no one else has been able to help before then.<br> <br> As far as the documentation goes, there have been major changes to the deployment process over the last few months and unfortunately, the documentation simply hasn't caught up and for that, I apologize. It should be updated in the near future to reflect the changes that have been made.</div> <div class="gmail_extra"><br> </div> <div class="gmail_extra">Best regards,</div> <div class="gmail_extra"><br clear="all"> <div> <div class="gmail_signature" data-smartmail="gmail_signature"> <div dir="ltr">-Phillip Bailey</div> </div> </div> <br> <div class="gmail_quote">On Tue, May 1, 2018 at 7:43 AM, Paul.LKW <span dir="ltr"><<a href="mailto:paul.lkw@gmail.com" target="_blank" moz-do-not-send="true">paul.lkw@gmail.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear All:<br> Recently I just make a try to create a Self-Hosted Engine oVirt but unfortunately both two of my box also failed with bad deployment experience, first of all the online documentation is wrong under "oVirt Self-Hosted Engine Guide" section, it says the deployment script "hosted-engine --deploy" will asking for Storage configuration immediately but it is not true any more, also on both of my 2 box one is configured with bond interface and one not but also failed, in order to separate the issue I think better I post the bonded interface one log for all your to Ref. first, the script runs at "TASK [Wait for the host to be up]" for long long time then give me the Error<br> <br> [ ERROR ] fatal: [localhost]: FAILED! => {"ansible_facts": {"ovirt_hosts": []}, "attempts": 120, "changed": false}<br> [ INFO ] TASK [include_tasks]<br> [ INFO ] ok: [localhost]<br> [ INFO ] TASK [Remove local vm dir]<br> [ INFO ] changed: [localhost]<br> [ INFO ] TASK [Notify the user about a failure]<br> [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"}<br> [ ERROR ] [DEPRECATION WARNING]: Using tests as filters is deprecated. Instead of using<br> [ ERROR ] `result|succeeded` instead use `result is succeeded`. This feature will be<br> [ ERROR ] removed in version 2.9. Deprecation warnings can be disabled by setting<br> [ ERROR ] deprecation_warnings=False in ansible.cfg.<br> [ ERROR ] [DEPRECATION WARNING]: Using tests as filters is deprecated. Instead of using<br> [ ERROR ] `result|succeeded` instead use `result is succeeded`. This feature will be<br> [ ERROR ] removed in version 2.9. Deprecation warnings can be disabled by setting<br> [ ERROR ] deprecation_warnings=False in ansible.cfg.<br> [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook<br> [ INFO ] Stage: Clean up<br> [ INFO ] Cleaning temporary resources<br> [ INFO ] TASK [Gathering Facts]<br> [ INFO ] ok: [localhost]<br> [ INFO ] TASK [include_tasks]<br> [ INFO ] ok: [localhost]<br> [ INFO ] TASK [Remove local vm dir]<br> [ INFO ] ok: [localhost]<br> [ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine-<wbr>setup/answers/answers-20180501<wbr>190540.conf'<br> [ INFO ] Stage: Pre-termination<br> [ INFO ] Stage: Termination<br> [ ERROR ] Hosted Engine deployment failed: please check the logs for the issue, fix accordingly or re-deploy from scratch.<br> Log file is located at /var/log/ovirt-hosted-engine-s<wbr>etup/ovirt-hosted-engine-setup<wbr>-20180501184459-4v6ctw.log<br> <br> Attached is the so long LOG.<br> <br> <br> <br> ______________________________<wbr>_________________<br> Users mailing list<br> <a href="mailto:Users@ovirt.org" moz-do-not-send="true">Users@ovirt.org</a><br> <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br> <br> </blockquote> </div> <br> </div> </div> </blockquote> <br> </body> </html> --------------DF05F08A6421548E64556F4E--
Can you provide other logs, vdsm log, for example? The installation of the Engine seem to have succeeded, then it tried to add the host. It was waiting for quite some time to get the host into 'Up' state. If, for example, it was installing packages, and the yum repo was very slow, that may be a reason. But there may be many other reasons as well. Y. On Tue, May 1, 2018 at 2:43 PM, Paul.LKW <paul.lkw@gmail.com> wrote:
Dear All: Recently I just make a try to create a Self-Hosted Engine oVirt but unfortunately both two of my box also failed with bad deployment experience, first of all the online documentation is wrong under "oVirt Self-Hosted Engine Guide" section, it says the deployment script "hosted-engine --deploy" will asking for Storage configuration immediately but it is not true any more, also on both of my 2 box one is configured with bond interface and one not but also failed, in order to separate the issue I think better I post the bonded interface one log for all your to Ref. first, the script runs at "TASK [Wait for the host to be up]" for long long time then give me the Error
[ ERROR ] fatal: [localhost]: FAILED! => {"ansible_facts": {"ovirt_hosts": []}, "attempts": 120, "changed": false} [ INFO ] TASK [include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [Remove local vm dir] [ INFO ] changed: [localhost] [ INFO ] TASK [Notify the user about a failure] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"} [ ERROR ] [DEPRECATION WARNING]: Using tests as filters is deprecated. Instead of using [ ERROR ] `result|succeeded` instead use `result is succeeded`. This feature will be [ ERROR ] removed in version 2.9. Deprecation warnings can be disabled by setting [ ERROR ] deprecation_warnings=False in ansible.cfg. [ ERROR ] [DEPRECATION WARNING]: Using tests as filters is deprecated. Instead of using [ ERROR ] `result|succeeded` instead use `result is succeeded`. This feature will be [ ERROR ] removed in version 2.9. Deprecation warnings can be disabled by setting [ ERROR ] deprecation_warnings=False in ansible.cfg. [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook [ INFO ] Stage: Clean up [ INFO ] Cleaning temporary resources [ INFO ] TASK [Gathering Facts] [ INFO ] ok: [localhost] [ INFO ] TASK [include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [Remove local vm dir] [ INFO ] ok: [localhost] [ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine- setup/answers/answers-20180501190540.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Hosted Engine deployment failed: please check the logs for the issue, fix accordingly or re-deploy from scratch. Log file is located at /var/log/ovirt-hosted-engine-s etup/ovirt-hosted-engine-setup-20180501184459-4v6ctw.log
Attached is the so long LOG.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
I ran through this again to regenerate the logs. It's been 100% repeatable for me on a fresh 7.4 install, running 'hosted-engine --deploy' or the preconfigured storage option in the cockpit oVirt UI. Deploying hyperconverged from the cockpit UI worked, however. Attaching contents of /var/log from hosted-engine and the physical host. This is what I got from 'journalctl -u vdsmd', wasn't reflected in VDSM logs. May 01 11:01:27 sum-glovirt-05.dy.gl systemd[1]: Starting Virtual Desktop Server Manager... May 01 11:01:27 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: vdsm: Running mkdirs May 01 11:01:27 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: vdsm: Running configure_coredump May 01 11:01:27 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: vdsm: Running configure_vdsm_logs May 01 11:01:27 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: vdsm: Running wait_for_network May 01 11:01:27 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: vdsm: Running run_init_hooks May 01 11:01:27 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: vdsm: Running check_is_configured May 01 11:01:27 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: abrt is already configured for vdsm May 01 11:01:27 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: lvm is configured for vdsm May 01 11:01:27 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: libvirt is already configured for vdsm May 01 11:01:27 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: Current revision of multipath.conf detected, preserving May 01 11:01:28 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: schema is already configuredvdsm: Running validate_configuration May 01 11:01:28 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: SUCCESS: ssl configured to true. No conflicts May 01 11:01:28 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: vdsm: Running prepare_transient_repository May 01 11:01:28 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: vdsm: Running syslog_available May 01 11:01:28 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: vdsm: Running nwfilter May 01 11:01:28 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: libvirt: Network Filter Driver error : this function is not supported by the connection driver: virNWFilterLookupByName May 01 11:01:28 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: libvirt: Network Filter Driver error : this function is not supported by the connection driver: virNWFilterDefineXML May 01 11:01:28 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: Traceback (most recent call last): May 01 11:01:28 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: File "/usr/bin/vdsm-tool", line 219, in main May 01 11:01:28 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: return tool_command[cmd]["command"](*args) May 01 11:01:28 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: File "/usr/lib/python2.7/site-packages/vdsm/tool/nwfilter.py", line 40, in main May 01 11:01:28 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: NoMacSpoofingFilter().defineNwFilter(conn) May 01 11:01:28 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: File "/usr/lib/python2.7/site-packages/vdsm/tool/nwfilter.py", line 76, in defineNwFilter May 01 11:01:28 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: nwFilter = conn.nwfilterDefineXML(self.buildFilterXml()) May 01 11:01:28 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py", line 130, in wrapper May 01 11:01:28 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: ret = f(*args, **kwargs) May 01 11:01:28 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 92, in wrapper May 01 11:01:28 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: return func(inst, *args, **kwargs) May 01 11:01:28 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: File "/usr/lib64/python2.7/site-packages/libvirt.py", line 4279, in nwfilterDefineXML May 01 11:01:28 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: if ret is None:raise libvirtError('virNWFilterDefineXML() failed', conn=self) May 01 11:01:28 sum-glovirt-05.dy.gl vdsmd_init_common.sh[15467]: libvirtError: this function is not supported by the connection driver: virNWFilterDefineXML May 01 11:01:28 sum-glovirt-05.dy.gl systemd[1]: vdsmd.service: control process exited, code=exited status=1 May 01 11:01:28 sum-glovirt-05.dy.gl systemd[1]: Failed to start Virtual Desktop Server Manager. May 01 11:01:28 sum-glovirt-05.dy.gl systemd[1]: Unit vdsmd.service entered failed state. May 01 11:01:28 sum-glovirt-05.dy.gl systemd[1]: vdsmd.service failed. May 01 11:01:29 sum-glovirt-05.dy.gl systemd[1]: vdsmd.service holdoff time over, scheduling restart. May 01 11:01:29 sum-glovirt-05.dy.gl systemd[1]: start request repeated too quickly for vdsmd.service May 01 11:01:29 sum-glovirt-05.dy.gl systemd[1]: Failed to start Virtual Desktop Server Manager. May 01 11:01:29 sum-glovirt-05.dy.gl systemd[1]: Unit vdsmd.service entered failed state. May 01 11:01:29 sum-glovirt-05.dy.gl systemd[1]: vdsmd.service failed. On Tue, May 1, 2018 at 10:18 AM, Yaniv Kaul <ykaul@redhat.com> wrote:
Can you provide other logs, vdsm log, for example? The installation of the Engine seem to have succeeded, then it tried to add the host. It was waiting for quite some time to get the host into 'Up' state. If, for example, it was installing packages, and the yum repo was very slow, that may be a reason. But there may be many other reasons as well. Y.
On Tue, May 1, 2018 at 2:43 PM, Paul.LKW <paul.lkw@gmail.com> wrote:
Dear All: Recently I just make a try to create a Self-Hosted Engine oVirt but unfortunately both two of my box also failed with bad deployment experience, first of all the online documentation is wrong under "oVirt Self-Hosted Engine Guide" section, it says the deployment script "hosted-engine --deploy" will asking for Storage configuration immediately but it is not true any more, also on both of my 2 box one is configured with bond interface and one not but also failed, in order to separate the issue I think better I post the bonded interface one log for all your to Ref. first, the script runs at "TASK [Wait for the host to be up]" for long long time then give me the Error
[ ERROR ] fatal: [localhost]: FAILED! => {"ansible_facts": {"ovirt_hosts": []}, "attempts": 120, "changed": false} [ INFO ] TASK [include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [Remove local vm dir] [ INFO ] changed: [localhost] [ INFO ] TASK [Notify the user about a failure] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"} [ ERROR ] [DEPRECATION WARNING]: Using tests as filters is deprecated. Instead of using [ ERROR ] `result|succeeded` instead use `result is succeeded`. This feature will be [ ERROR ] removed in version 2.9. Deprecation warnings can be disabled by setting [ ERROR ] deprecation_warnings=False in ansible.cfg. [ ERROR ] [DEPRECATION WARNING]: Using tests as filters is deprecated. Instead of using [ ERROR ] `result|succeeded` instead use `result is succeeded`. This feature will be [ ERROR ] removed in version 2.9. Deprecation warnings can be disabled by setting [ ERROR ] deprecation_warnings=False in ansible.cfg. [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook [ INFO ] Stage: Clean up [ INFO ] Cleaning temporary resources [ INFO ] TASK [Gathering Facts] [ INFO ] ok: [localhost] [ INFO ] TASK [include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [Remove local vm dir] [ INFO ] ok: [localhost] [ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine- setup/answers/answers-20180501190540.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Hosted Engine deployment failed: please check the logs for the issue, fix accordingly or re-deploy from scratch. Log file is located at /var/log/ovirt-hosted-engine-s etup/ovirt-hosted-engine-setup-20180501184459-4v6ctw.log
Attached is the so long LOG.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
This is a multi-part message in MIME format. --------------52C5D9E92E259DD5E31E2804 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Dear Y: Yes you are right I could see there is a VM up process from "top" list 11273 qemu 20 0 4896964 3.066g 13456 S 5.0 9.8 25:36.69 /usr/libexec/qemu-kvm -name guest=HostedEngineLocal,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-3-HostedEngineLocal/m+................... but however vdsm.log is zero length. Best Regards, Paul.LKW Yaniv Kaul 於 1/5/2018 22:18 寫道:
Can you provide other logs, vdsm log, for example? The installation of the Engine seem to have succeeded, then it tried to add the host. It was waiting for quite some time to get the host into 'Up' state. If, for example, it was installing packages, and the yum repo was very slow, that may be a reason. But there may be many other reasons as well. Y.
On Tue, May 1, 2018 at 2:43 PM, Paul.LKW <paul.lkw@gmail.com <mailto:paul.lkw@gmail.com>> wrote:
Dear All: Recently I just make a try to create a Self-Hosted Engine oVirt but unfortunately both two of my box also failed with bad deployment experience, first of all the online documentation is wrong under "oVirt Self-Hosted Engine Guide" section, it says the deployment script "hosted-engine --deploy" will asking for Storage configuration immediately but it is not true any more, also on both of my 2 box one is configured with bond interface and one not but also failed, in order to separate the issue I think better I post the bonded interface one log for all your to Ref. first, the script runs at "TASK [Wait for the host to be up]" for long long time then give me the Error
[ ERROR ] fatal: [localhost]: FAILED! => {"ansible_facts": {"ovirt_hosts": []}, "attempts": 120, "changed": false} [ INFO ] TASK [include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [Remove local vm dir] [ INFO ] changed: [localhost] [ INFO ] TASK [Notify the user about a failure] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"} [ ERROR ] [DEPRECATION WARNING]: Using tests as filters is deprecated. Instead of using [ ERROR ] `result|succeeded` instead use `result is succeeded`. This feature will be [ ERROR ] removed in version 2.9. Deprecation warnings can be disabled by setting [ ERROR ] deprecation_warnings=False in ansible.cfg. [ ERROR ] [DEPRECATION WARNING]: Using tests as filters is deprecated. Instead of using [ ERROR ] `result|succeeded` instead use `result is succeeded`. This feature will be [ ERROR ] removed in version 2.9. Deprecation warnings can be disabled by setting [ ERROR ] deprecation_warnings=False in ansible.cfg. [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook [ INFO ] Stage: Clean up [ INFO ] Cleaning temporary resources [ INFO ] TASK [Gathering Facts] [ INFO ] ok: [localhost] [ INFO ] TASK [include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [Remove local vm dir] [ INFO ] ok: [localhost] [ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20180501190540.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Hosted Engine deployment failed: please check the logs for the issue, fix accordingly or re-deploy from scratch. Log file is located at /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20180501184459-4v6ctw.log
Attached is the so long LOG.
_______________________________________________ Users mailing list Users@ovirt.org <mailto:Users@ovirt.org> http://lists.ovirt.org/mailman/listinfo/users <http://lists.ovirt.org/mailman/listinfo/users>
--------------52C5D9E92E259DD5E31E2804 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> <p>Dear Y:<br> Yes you are right I could see there is a VM up process from "top" list<br> <br> 11273 qemu 20 0 4896964 3.066g 13456 S 5.0 9.8 25:36.69 /usr/libexec/qemu-kvm -name guest=HostedEngineLocal,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-3-HostedEngineLocal/m+...................<br> </p> but however vdsm.log is zero length.<br> <br> Best Regards,<br> Paul.LKW<br> <br> <br> <div class="moz-cite-prefix">Yaniv Kaul 於 1/5/2018 22:18 寫道:<br> </div> <blockquote type="cite" cite="mid:CAJgorsZfrNbkwJDchMk73C0rLz-U93jCcNuK_TfqL6vHAN8jdg@mail.gmail.com"> <div dir="ltr">Can you provide other logs, vdsm log, for example? <div>The installation of the Engine seem to have succeeded, then it tried to add the host. It was waiting for quite some time to get the host into 'Up' state.</div> <div>If, for example, it was installing packages, and the yum repo was very slow, that may be a reason.</div> <div>But there may be many other reasons as well.</div> <div>Y.</div> </div> <div class="gmail_extra"><br> <div class="gmail_quote">On Tue, May 1, 2018 at 2:43 PM, Paul.LKW <span dir="ltr"><<a href="mailto:paul.lkw@gmail.com" target="_blank" moz-do-not-send="true">paul.lkw@gmail.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear All:<br> Recently I just make a try to create a Self-Hosted Engine oVirt but unfortunately both two of my box also failed with bad deployment experience, first of all the online documentation is wrong under "oVirt Self-Hosted Engine Guide" section, it says the deployment script "hosted-engine --deploy" will asking for Storage configuration immediately but it is not true any more, also on both of my 2 box one is configured with bond interface and one not but also failed, in order to separate the issue I think better I post the bonded interface one log for all your to Ref. first, the script runs at "TASK [Wait for the host to be up]" for long long time then give me the Error<br> <br> [ ERROR ] fatal: [localhost]: FAILED! => {"ansible_facts": {"ovirt_hosts": []}, "attempts": 120, "changed": false}<br> [ INFO ] TASK [include_tasks]<br> [ INFO ] ok: [localhost]<br> [ INFO ] TASK [Remove local vm dir]<br> [ INFO ] changed: [localhost]<br> [ INFO ] TASK [Notify the user about a failure]<br> [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"}<br> [ ERROR ] [DEPRECATION WARNING]: Using tests as filters is deprecated. Instead of using<br> [ ERROR ] `result|succeeded` instead use `result is succeeded`. This feature will be<br> [ ERROR ] removed in version 2.9. Deprecation warnings can be disabled by setting<br> [ ERROR ] deprecation_warnings=False in ansible.cfg.<br> [ ERROR ] [DEPRECATION WARNING]: Using tests as filters is deprecated. Instead of using<br> [ ERROR ] `result|succeeded` instead use `result is succeeded`. This feature will be<br> [ ERROR ] removed in version 2.9. Deprecation warnings can be disabled by setting<br> [ ERROR ] deprecation_warnings=False in ansible.cfg.<br> [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook<br> [ INFO ] Stage: Clean up<br> [ INFO ] Cleaning temporary resources<br> [ INFO ] TASK [Gathering Facts]<br> [ INFO ] ok: [localhost]<br> [ INFO ] TASK [include_tasks]<br> [ INFO ] ok: [localhost]<br> [ INFO ] TASK [Remove local vm dir]<br> [ INFO ] ok: [localhost]<br> [ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine-<wbr>setup/answers/answers-20180501<wbr>190540.conf'<br> [ INFO ] Stage: Pre-termination<br> [ INFO ] Stage: Termination<br> [ ERROR ] Hosted Engine deployment failed: please check the logs for the issue, fix accordingly or re-deploy from scratch.<br> Log file is located at /var/log/ovirt-hosted-engine-s<wbr>etup/ovirt-hosted-engine-setup<wbr>-20180501184459-4v6ctw.log<br> <br> Attached is the so long LOG.<br> <br> <br> <br> ______________________________<wbr>_________________<br> Users mailing list<br> <a href="mailto:Users@ovirt.org" moz-do-not-send="true">Users@ovirt.org</a><br> <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br> <br> </blockquote> </div> <br> </div> </blockquote> <br> </body> </html> --------------52C5D9E92E259DD5E31E2804--
participants (4)
-
Joe DiTommasso -
Paul.LKW -
Phillip Bailey -
Yaniv Kaul