3:07 a.m.
On Thu, Sep 17, 2020 at 8:16 AM Adam Xu <adam_xu(a)adagene.com.cn> wrote:
在 2020/9/16 15:53, Yedidyah Bar David 写道:
> On Wed, Sep 16, 2020 at 10:46 AM Adam Xu <adam_xu(a)adagene.com.cn> wrote:
>> 在 2020/9/16 15:12, Yedidyah Bar David 写道:
>>> On Wed, Sep 16, 2020 at 6:10 AM Adam Xu <adam_xu(a)adagene.com.cn>
wrote:
>>>> Hi ovirt
>>>>
>>>> I just try to upgrade a self-Hosted engine from 4.3.10 to 4.4.1.4. I
followed the step in the document:
>>>>
>>>>
https://www.ovirt.org/documentation/upgrade_guide/#SHE_Upgrading_from_4-3
>>>>
>>>> the old 4.3 env has a FC storage as engine storage domain and I have
created a new FC storage vv for the new storage domain to be used in the next steps.
>>>>
>>>> I backup the old 4.3 env and prepare a total new host to restore the
env.
>>>>
>>>> in charter 4.4 step 8, it said:
>>>>
>>>> "During the deployment you need to provide a new storage domain.
The deployment script renames the 4.3 storage domain and retains its data."
>>>>
>>>> it does rename the old storage domain. but it didn't let me choose a
new storage domain during the deployment. So the new enigne just deployed in the new
host's local storage and can not move to the FC storage domain.
>>>>
>>>> Can anyone tell me what the problem is?
>>> What do you mean in "deployed in the new host's local
storage"?
>>>
>>> Did deploy finish successfully?
>> I think it was not finished yet.
> You did 'hosted-engine --deploy --restore-from-file=something', right?
>
> Did this finish?
not finished yet.
>
> What are the last few lines of the output?
[ INFO ] You can now connect to
https://ovirt6.ntbaobei.com:6900/ovirt-engine/ and check the status of
this host and eventually remediate it, please continue only when the
host is listed as 'up'
[ INFO ] TASK [ovirt.hosted_engine_setup : include_tasks]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Create temporary lock file]
[ INFO ] changed: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Pause execution until
/tmp/ansible.g2opa_y6_he_setup_lock is removed, delete it once ready to
proceed]
Great. This means that you replied 'Yes' to 'Pause the execution
after adding this host to the engine?', and it's now waiting.
but the new host which run the self-hosted engine's status is
"NonOperational" and never will be "up"
You seem to to imply that you expected it to become "up" by itself,
and that you claim that this will never happen, in which you are
correct.
But that's not the intention. The message you got is:
You will be able to iteratively connect to the restored engine in
order to manually review and remediate its configuration before
proceeding with the deployment:
please ensure that all the datacenter hosts and storage domain are
listed as up or in maintenance mode before proceeding.
This is normally not required when restoring an up to date and
coherent backup.
This means that it's up to you to handle this nonoperational host,
and that you are requested to continue (by removing that file) only
then.
So now, let's try to understand why the host is nonoperational, and
try to fix that. Ok?
You should be able to find the current (private/local) IP address of
the engine vm by searching the hosted-engine setup logs for 'local_vm_ip'.
You can ssh (and scp etc.) there from the host, using user 'root' and
the password you supplied.
Please check/share all of /var/log/ovirt-engine on the engine vm.
In particular, please check host-deploy/* logs there. The last lines
show a summary, like:
HOSTNAME : ok=97 changed=34 unreachable=0 failed=0
skipped=46 rescued=0 ignored=1
Is 'failed' higher than 0? If so, please find the failed task and
check/share the relevant error (or just the entire file).
Also, please check engine.log there for any ' ERROR '.
Good luck and best regards,
>
> Please also check/share logs from /var/log/ovirt-hosted-engine-setup/*
> (including subdirs).
> no more errers there, just a lot of DEBUG messages.
>> It didn't tell me to choose a new
>> storage domain and just give me the new hosts fqdn as the engine's URL.
>> like host6.example.com:6900 .
> Yes, that's temporarily, to let you access the engine VM (on the local
network).
>
>> I can login use the host6.example.com:6900 and I saw the engine vm ran
>> in host6's /tmp dir.
>>
>>> HE deploy (since 4.3) first creates a VM for the engine on local
>>> storage, then prompts you to provide the storage you want to use, and
>>> then moves the VM disk image there.
>>>
>>> Best regards,
>>>
>>>> Thanks
>>>>
>>>> --
>>>> Adam Xu
>>>>
>>>> _______________________________________________
>>>> Users mailing list -- users(a)ovirt.org
>>>> To unsubscribe send an email to users-leave(a)ovirt.org
>>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>>>> oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
>>>> List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/XHDGJB2ZAFS...
>>>
>> --
>> Adam Xu
>> Phone: 86-512-8777-3585
>> Adagene (Suzhou) Limited
>> C14, No. 218, Xinghu Street, Suzhou Industrial Park
>>
>> _______________________________________________
>> Users mailing list -- users(a)ovirt.org
>> To unsubscribe send an email to users-leave(a)ovirt.org
>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>> oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/RLOBPKLW7OB...
>
>
--
Adam Xu
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/UTVZW7W6XHZ...
--
Didi