Thank you so much for the detailed response!
You can try looking at the dwh_history_timekeeping table in the engine (not dwh) database:
su - postgres -c 'psql engine -c "select * from dwh_history_timekeeping;"'
Most likely you'll find there more than one line with var_name 'lastSync’.
And that I most certainly did. There were double of each var_name. I simply deleted one of each of the pairs that made the most sense to delete, reran engine-setup and all appears to be working now!
How this happened is quite interesting/useful to know, because it should not normally happen, and is most likely a bug. If you can reproduce this, please file a bug with relevant details. Thanks!
I’m pretty sure this was a self-inflicted issue as a while back when things broke, we actually had two oVirt heads running but we didn’t catch it for a while. Basically, we migrated from a VM running the head (on a separate VM solution) to a hardware solution. Someone ended up turning the VM back on and it started wreaking havoc on our installation. This was likely a leftover from that condition. If it happens to return, I’ll be sure to file a bug. One last question: Data for the Storage section of the Global Utilization part of the dashboard is empty. We are using Ceph via Cinder for our storage. Is that the issue? Side note: we are now being bitten by this bug - https://bugzilla.redhat.com/show_bug.cgi?id=1465825 Thanks again for the assistance. Charles