7:25 a.m.
Dear Team,
We have setup of 3 node cluster with 3.4 version of ovirt, after node server
restart, hosted engine showing as "vm not running on this host" on 2 nodes
and it is running on only one node. Please find screen shot below,
--== Host 1 status ==--
Status up-to-date : True
Hostname : node2.ctelhyd.in
Host ID : 1
Engine status : {"reason": "vm not running on this
host", "health": "bad", "vm": "down",
"detail": "unknown"}
Score : 3400
stopped : False
Local maintenance : False
crc32 : 04c18d76
Host timestamp : 231158
--== Host 2 status ==--
Status up-to-date : True
Hostname : node3.ctelhyd.in
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 : f0b6a1b2
Host timestamp : 231171
--== Host 3 status ==--
Status up-to-date : True
Hostname : node1.ctelhyd.in
Host ID : 3
Engine status : {"health": "good",
"vm": "up",
"detail": "up"}
Score : 3400
stopped : False
Local maintenance : False
crc32 : 7ef5dd17
Host timestamp : 231223
Thanks & Regards,
Syed Abdul Qadeer.
7660022818.
8:17 a.m.
On Tue, 2018-06-26 at 09:55 +0530, syedquadeer(a)ctel.in wrote:
Dear Team,
We have setup of 3 node cluster with 3.4 version of ovirt, after node
server restart, hosted engine showing as “vm not running on this
host” on 2 nodes and it is running on only one node.
Well, thank god for that! If it was running on more than one node at a
time, it would write itself to pieces!
But seriously, what´s the problem? What you´re describing is exactly
how it´s supposed to be:) And for what it´s worth, do yourself a favor
and upgrade, 3.4 has been EOL for a looong time now.
/K
Please find screen shot below,
--== Host 1 status ==--
Status up-to-date : True
Hostname : node2.ctelhyd.in
Host ID : 1
Engine status : {"reason": "vm not running on
this host", "health": "bad", "vm": "down",
"detail": "unknown"}
Score : 3400
stopped : False
Local maintenance : False
crc32 : 04c18d76
Host timestamp : 231158
--== Host 2 status ==--
Status up-to-date : True
Hostname : node3.ctelhyd.in
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 : f0b6a1b2
Host timestamp : 231171
--== Host 3 status ==--
Status up-to-date : True
Hostname : node1.ctelhyd.in
Host ID : 3
Engine status : {"health": "good",
"vm": "up",
"detail": "up"}
Score : 3400
stopped : False
Local maintenance : False
crc32 : 7ef5dd17
Host timestamp : 231223
Thanks & Regards,
Syed Abdul Qadeer.
7660022818.
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/communit
y-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/
message/BTHAACGS6N2OHFEPUKAFLLGQLVGOBBAO/
8:41 a.m.
When I check /var/log/ovirt-hosted-engine-ha/agent.log it is giving below error in all
three nodes
MainThread::WARNING::2018-06-26
11:09:20,879::ovf_store::104::ovirt_hosted_engine_ha.lib.ovf.ovf_store.OVFStore::(scan)
Unable to find OVF_STORE
MainThread::ERROR::2018-06-26
11:09:20,898::config::235::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config::(refresh_local_conf_file)
Unable to get vm.conf from OVF_STORE, falling back to initial vm.conf
-----Original Message-----
From: Karli Sjöberg <karli(a)inparadise.se>
Sent: Tuesday, June 26, 2018 10:47 AM
To: syedquadeer(a)ctel.in; users(a)ovirt.org
Subject: Re: [ovirt-users] Reg: Hosted-engine "vm not running on this host"
On Tue, 2018-06-26 at 09:55 +0530, syedquadeer(a)ctel.in wrote:
Dear Team,
We have setup of 3 node cluster with 3.4 version of ovirt, after node
server restart, hosted engine showing as “vm not running on this host”
on 2 nodes and it is running on only one node.
Well, thank god for that! If it was running on more than one node at a time, it would
write itself to pieces!
But seriously, what´s the problem? What you´re describing is exactly how it´s supposed to
be:) And for what it´s worth, do yourself a favor and upgrade, 3.4 has been EOL for a
looong time now.
/K
Please find screen shot below,
--== Host 1 status ==--
Status up-to-date : True
Hostname : node2.ctelhyd.in
Host ID : 1
Engine status : {"reason": "vm not running on
this host", "health": "bad", "vm": "down",
"detail": "unknown"}
Score : 3400
stopped : False
Local maintenance : False
crc32 : 04c18d76
Host timestamp : 231158
--== Host 2 status ==--
Status up-to-date : True
Hostname : node3.ctelhyd.in
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 : f0b6a1b2
Host timestamp : 231171
--== Host 3 status ==--
Status up-to-date : True
Hostname : node1.ctelhyd.in
Host ID : 3
Engine status : {"health": "good",
"vm": "up",
"detail": "up"}
Score : 3400
stopped : False
Local maintenance : False
crc32 : 7ef5dd17
Host timestamp : 231223
Thanks & Regards,
Syed Abdul Qadeer.
7660022818.
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org Privacy
Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/communit
y-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/
message/BTHAACGS6N2OHFEPUKAFLLGQLVGOBBAO/
2341
days inactive
2341
days old
2 comments
2 participants
participants (2)
-
Karli Sjöberg -
syedquadeer＠ctel.in