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 <[email protected] <mailto:[email protected]>> 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
    [email protected] <mailto:[email protected]>
    http://lists.ovirt.org/mailman/listinfo/users
    <http://lists.ovirt.org/mailman/listinfo/users>



_______________________________________________
Users mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/users

Reply via email to