Hide Forgot
Description of problem: Date/time configuration should be mentioned in the engine best practices document. For example, while engine time is few hours late/early, it could result in accounts cannot access with 'account has expired' issues as reported in https://bugzilla.redhat.com/show_bug.cgi?id=1273297 Version-Release number of selected component (if applicable): rhevm-3.6.0.1-0.1.el6.noarch rhevm-doc-3.6.0-1.el6eng.noarch
hi Elad, Do you mean users should set up NTP on the Manager to avoid the issue you have described? I see a workaround has been provided in BZ#1171474: --- Work around is to configure ntpd service to run on boot "chkconfig ntpd on" and to set ntp config file for correct ntp server "vi /etc/ntp.conf" clock.redhat.com --- Is this what you are after? Cheers, Julie
Hi Julie, Yes, this is what I mean.
Added an additional step to the Configuring the Red Hat Enterprise Virtualization Manager section in the Installation Guide: ---- If you intend to link your Red Hat Enterprise Virtualization environment with a directory server, configure the date and time to synchronize with the system clock used by the directory server to avoid unexpected account expiry issues. See <ulink url="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html">Red Hat Enterprise Linux Deployment Guide, Configure NTP</ulink> for more information. ---- Hi Elad, Could you confirm if the note is correct? Cheers, Julie
Yes
Reviewed and merged. Looks good to me. Moving to VERIFIED.