Hide Forgot
Description of problem: When verifying the qmf "plugins" on windows, I had notice the DaemonStartTime appeared to be 5 hours into the future, unless we are normalizing to GMT. Version-Release number of selected component (if applicable): latest-devel How reproducible: 100% Steps to Reproduce: 1. Startup condor on windows. Actual results: +5 hours into the future. Expected results: something local to the qmf host.
What was version of condor-qmf and qpid* where you found this bug?
qpid: list master Object Summary: ID Created Destroyed Index ============================================================== 185 16:38:16 - <snip> qpid: show 185 Object of type: com.redhat.grid:master:_data(0f48db16-7d60-7f0d-d8f4-381ad78a8914) Attribute 185 ================================================================================================================ CondorPlatform $CondorPlatform: X86_64-Fedora_16 $ CondorVersion $CondorVersion: 7.6.8 Apr 30 2012 BuildID: pmackinn_local PRE-RELEASE-UWCS $ DaemonStartTime Wed May 2 16:38:16 2012 $ date Wed May 2 12:45:21 EDT 2012 $ condor_status -master -long | grep DaemonStartTime DaemonStartTime = 1335976696 $ date -ud @1335976696 Wed May 2 16:38:16 UTC 2012
Was it tested on RHEL5/6 too?
Yes