Description of problem: IMO this message is not the best one: ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(consume) Engine vm running on localhost Imagine one uses some loghost and read a log for example in kibana and what does 'localhost' tells him? Not much, right? So I suppose it is changed to: ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(consume) Engine vm running on local host ($host) Version-Release number of selected component (if applicable): 3.5.4 How reproducible: 100% Steps to Reproduce: 1. have self-hosted engine on two nodes 2. observe /var/log/ovirt-hosted-engine-ha/agent.log for the message 3. Actual results: ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(consume) Engine vm running on localhost Expected results: ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(consume) Engine vm running on local host ($host) Additional info:
Don't you see the host of origin when you merge logs from multiple machines or forward the syslog stream to a remote server? We would be duplicating that info..
My nitpicking is that localhost is so generic. And... does engine VM really runs on localhost? IMO localhost is lo* netiface but engine VM is not binded to 127.0.0.0/8 :P Anyway, localhost is not best word here. (Yes, logs can be prefixed by hostname string.)
Engine vm running locally ($host) ?
There's a way to see the HE VM location these days in the UI, as well as in the logs. We won't be perusing this issue any more. If someone needs it, patches are welcomed.