Hi Ryan and thanks for the quick reply. This is an entirely new system, no VM, no nothing. This was built for testing v4.1. I'll log a case with GSS on this if it is not normal. Bit confiused, so what do I need to do for the Installation -> Check for Upgrades to work in RHV-M? I'm using an old RHEV-H 7.1 image for the hypervisors so there should definitely be an upgrade available. Also, any thoughts on the webUI timeout? Thanks again CC On Thu, Sep 14, 2017 at 8:45 PM, Ryan Barry <rbarry@redhat.com> wrote:
On Thu, Sep 14, 2017 at 8:36 AM, Colin Coe <colin.coe@gmail.com> wrote:
Hi all
We're in the process of upgrading from RHEV 3.5 to 4.1.5 and I have a couple of questions.
RHV 4.1.5 takes between 10-15 minutes to become usable after a service restart, is this expected or is something wrong with our environment?
10-15 minutes seems long, but it depends on the database. How much historical data is present?
The webUI seems to timeout and go back to the logon page after a very short time. Can this behavior be changed?
Lastly, the RH318 course book states that to upgrade a RHEV-H node via RHEV-M, you need to install the "rhev-hypervisor7" package on the RHEV-M node. Is this still correct?
Node/RHVH for 4.x now upgrades straight from yum, so nothing is needed on the engine :)
Thanks
CC
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--
RYAN BARRY
SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHEV HYPERVISOR
Red Hat NA <https://www.redhat.com/>
rbarry@redhat.com M: +1-651-815-9306 IM: rbarry <https://red.ht/sig>