Latest update - the system is back and running normally.After a day (or maybe
a little more), the OVF is OK:
[root@ovirt1 ~]# ls -l
/rhev/data-center/mnt/glusterSD/ovirt1.localdomain\:_engine/808423f9-8a5c-40cd-bc9f-2568c85b8c74/images/{441abdc8-6cb1-49a4-903f-a1ec0ed88429,94ade632-6ecc-4901-8cec-8e39f3d69cb0}
/rhev/data-center/mnt/glusterSD/ovirt1.localdomain:_engine/808423f9-8a5c-40cd-bc9f-2568c85b8c74/images/441abdc8-6cb1-49a4-903f-a1ec0ed88429:
total 66591
-rw-rw----. 1 vdsm kvm 30720 Mar 12 08:06 c3309fc0-8707-4de1-903d-8d4bbb024f81
-rw-rw----. 1 vdsm kvm 1048576 Jan 31 13:24
c3309fc0-8707-4de1-903d-8d4bbb024f81.lease
-rw-r--r--. 1 vdsm kvm 435 Mar 12 08:06
c3309fc0-8707-4de1-903d-8d4bbb024f81.meta
/rhev/data-center/mnt/glusterSD/ovirt1.localdomain:_engine/808423f9-8a5c-40cd-bc9f-2568c85b8c74/images/94ade632-6ecc-4901-8cec-8e39f3d69cb0:
total 66591
-rw-rw----. 1 vdsm kvm 30720 Mar 12 08:06 9460fc4b-54f3-48e3-b7b6-da962321ecf4
-rw-rw----. 1 vdsm kvm 1048576 Jan 31 13:24
9460fc4b-54f3-48e3-b7b6-da962321ecf4.lease
-rw-r--r--. 1 vdsm kvm 435 Mar 12 08:06
9460fc4b-54f3-48e3-b7b6-da962321ecf4.meta
Once it's got fixed, I have managed to start the hosted-engine properly (I have
rebooted the whole cluster just to be on the safe side):
[root@ovirt1 ~]# hosted-engine --vm-status
--== Host ovirt1.localdomain (id: 1) status ==--
conf_on_shared_storage : True
Status up-to-date : True
Hostname : ovirt1.localdomain
Host ID : 1
Engine status : {"health": "good", "vm": "up", "detail":
"Up"}
Score : 3400
stopped : False
Local maintenance : False
crc32 : 8ec26591
local_conf_timestamp : 49704
Host timestamp : 49704
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=49704 (Tue Mar 12 10:47:43 2019)
host-id=1
score=3400
vm_conf_refresh_time=49704 (Tue Mar 12 10:47:43 2019)
conf_on_shared_storage=True
maintenance=False
state=EngineUp
stopped=False
--== Host ovirt2.localdomain (id: 2) status ==--
conf_on_shared_storage : True
Status up-to-date : True
Hostname : ovirt2.localdomain
Host ID : 2
Engine status : {"reason": "vm not running on this host",
"health": "bad", "vm": "down", "detail": "unknown"}
Score : 3400
stopped : False
Local maintenance : False
crc32 : f9f39dcd
local_conf_timestamp : 14458
Host timestamp : 14458
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=14458 (Tue Mar 12 10:47:41 2019)
host-id=2
score=3400
vm_conf_refresh_time=14458 (Tue Mar 12 10:47:41 2019)
conf_on_shared_storage=True
maintenance=False
state=EngineDown
stopped=False
Best Regards,Strahil Nikolov
В неделя, 10 март 2019 г., 5:05:33 ч. Гринуич+2, Strahil Nikolov
<[email protected]> написа:
Hello again,
Latest update: the engine is up and running (or at least the login portal).
[root@ovirt1 ~]# hosted-engine --check-livelinessHosted Engine is up!
I have found online the xml for the network:
[root@ovirt1 ~]# cat ovirtmgmt_net.xml <network> <name>vdsm-ovirtmgmt</name>
<forward mode='bridge'/> <bridge name='ovirtmgmt'/> </network>
Sadly, I had to create a symbolic link to the main disk in
/var/run/vdsm/storage , as it was missing.
So, what's next.
Issues up to now:2 OVF - 0 bytesProblem with local copy of the HostedEngine
config - used xml from an old vdsm logMissing vdsm-ovirtmgmt definitionNo link
for the main raw disk in /var/run/vdsm/storage .
Can you hint me how to recover the 2 OVF tars now ?
Best Regards,Strahil Nikolov
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/[email protected]/message/ODFPHVS5LYY6JWFWKWR3PBYTF3QSDKGV/
