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