[ovirt-users] Ovirt self-hosted engine won't come up

The self-hosted engine had an issue whereby it'd /var partition was full. A few days later the engine was rebooted; however, it did not come back up gracefully. I presently have three CentOS 7 hosts which can spin up a new hosted engine vm; however every attempt to do so results in: Engine status : {"reason": "failed liveliness check", "health": "bad", "vm": "up", "detail": "Up"} The VM is not "up" as it does not even respond to ping, let alone having any ability to ssh or console into it to see what's wrong. All of the VMs that have been built using this engine appear to be fully operational. Is there any guidance anyone can give me? At this point I'm wondering what the consequences are to deploying a new hosted engine within that same cluster. If anyone could shed light on this matter it would be tremendously appreciated! Thanks.