Description of problem: - RHEV-H is upgraded to 3.6 version - 2400 Score (it was looking to the shared storage for the vm.conf, but it wasn't there) - Hosted Storage was properly upgraded - still 2400 Score - Restarts of the HA services/whole host doesn't improve the situation A newly installed 3.6 Host in the HE environment had from the beginning 3400 score. We haven't reproduced it yet, but there are recent logs in the case #01619281 https://api.access.redhat.com/rs/cases/01619281/attachments/786f6ded-1dbf-4a22-92e3-2be40e24ae90 Version-Release number of selected component (if applicable): RHEV-Hypervisor 7.2 (20160328.0.el7ev) ovirt-hosted-engine-ha-1.3.5.1-1.el7ev.noarch Please let us know what else is needed for troubleshooting of this issue.
Nikolai I know you tested more than few scenarios with RHEVH - Did you see this happening?
(In reply to Roy Golan from comment #2) > Nikolai I know you tested more than few scenarios with RHEVH - Did you see > this happening? Not that I remember this happening, we also had no other choice, other than reprovisioning eh6-eh7, so once they were cleanly reprovisioned, I didn't seen this issue. I'd be asking Ying for if she saw this RHEVH problem too. Adding Ying to need info.
By the way, the customer formatted the Host, re-deployed it and now it has 3400 score. I am not sure if i can help you with any further logs/tests now.
(In reply to Nikolai Sednev from comment #3) > (In reply to Roy Golan from comment #2) > > Nikolai I know you tested more than few scenarios with RHEVH - Did you see > > this happening? > > Not that I remember this happening, we also had no other choice, other than > reprovisioning eh6-eh7, so once they were cleanly reprovisioned, I didn't > seen this issue. I'd be asking Ying for if she saw this RHEVH problem too. > Adding Ying to need info. IIRC, I did not encounter this issue with NFS storage before, and I didn't hear team feedback to me regarding to such issue before. I will check the bug attachment ID 01619281 later to know the exact steps and versions to reproduce it if needed. Thanks.
Ying any updates on the reproduce? if not reproducible I'll close it
(In reply to Roy Golan from comment #6) > Ying any updates on the reproduce? if not reproducible I'll close it Roy, I will work on this HE bug next week to try to reproduce it in-house, will give you update later. thanks
If you see this please reopen with reproducer and log.
# just for recording the update by this comment. For this bug, we still did not 100% know the steps to reproduce it in-house, just checking the customer ticket 01619281 which already was closed, the env. was about to iSCSI env. and set smtp server.