Bug 1331284

Created attachment 1151776 [details]
engine and server logs

Description of problem:
[RFE] - ovirt-engine service fails to start,  but systemd is unaware of that and consider it as running.

-We should report ovirt-engine service as active/running only if engine ear is actually deployed to jboss, not only when jboss server is running.

Version-Release number of selected component (if applicable):
4.0.0-0.0.master.20160423161403.gite38df80.el7.centos
systemd-219-19.el7_2.8.x86_64


Steps to Reproduce:
1. Enter to engine DB and insert a fake MAC pool id without range:
engine=# insert into mac_pools (id, name) values ('19479b7e-0ac5-11e6-a513-68f7280ce233', 'fake');
INSERT 0 1
2. Quit DB and restart ovirt-engine service
3. Run systemctl status ovirt-engine and try to login the engine UI

Actual results:
[root@dhcp160-211 ~]# systemctl status ovirt-engine
● ovirt-engine.service - oVirt Engine
   Loaded: loaded (/usr/lib/systemd/system/ovirt-engine.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2016-04-28 10:37:22 IDT; 6s ago
 Main PID: 21458 (ovirt-engine.py)
   CGroup: /system.slice/ovirt-engine.service
           ├─21458 /usr/bin/python /usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.py --redirect-output --systemd=notify start
           └─21489 ovirt-engine -server -XX:+TieredCompilation -Xms1024M -Xmx1024M -Djava.awt.headless=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djsse.enableSNIExtens...

Apr 28 10:37:18 dhcp160-211.scl.lab.tlv.redhat.com systemd[1]: Starting oVirt Engine...
Apr 28 10:37:22 dhcp160-211.scl.lab.tlv.redhat.com systemd[1]: Started oVirt Engine

- But engine UI isn't accessible. Engine actually fails to start and systemd isn't aware of that. 

Expected results:
Engine should fail to start and systemd should be aware of that

Additional info:
See also - BZ 1297402