Puppet users - May 2011 - report time determined by client not server?

Howdy,

I''ve just built a VM where the system clock was 2 hours off. Part of
the
puppet manifest is to get NTP going, so the system itself takes care of
itself OK. However I just noticed on Dashboard that the report listed for
the build phase was also two hours off. As such I''m given to assume
that the
official report time is actually taken from the client and not the puppet
master? To me, this makes no sense, and must surely be a bug. Why would you
ever want to trust a time stamp from the client instead of just using your
own time as you receive the report? Now the new VM has the correct time, the
new reports are listed as older as the build phase ones etc...

Thanks

Chris

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On May 13, 2011, at 8:36 AM, Chris Phillips wrote:
> Why would you ever want to trust a time stamp from the client instead of
just using your own time as you receive the report?
In my case, when I run the import rake task, it imports stored reports that
might be old.  This means that the time the report is imported into the server
is wrong and the time inside the report is correct.  I also hope that someday
puppet will have a system that can automatically queue reports that
can''t be sent and automatically send them later, though I''ll
admit I haven''t even cared enough to file a bug report.  If this
happens, you''d again want to trust the client''s time instead
of the server''s time.


If the system clock was wrong, I''m surprised SSL worked.

If the timezone was different, I''d suggest filing a bug report related
to puppet not using the timezone properly.

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Fri, May 13, 2011 at 6:36 PM, Chris Phillips <chris@untrepid.com>
wrote:
> Howdy,
>
> I''ve just built a VM where the system clock was 2 hours off. Part
of the
> puppet manifest is to get NTP going, so the system itself takes care of
> itself OK. However I just noticed on Dashboard that the report listed for
> the build phase was also two hours off. As such I''m given to
assume that the
> official report time is actually taken from the client and not the puppet
> master? To me, this makes no sense, and must surely be a bug. Why would you
> ever want to trust a time stamp from the client instead of just using your
> own time as you receive the report? Now the new VM has the correct time,
the
> new reports are listed as older as the build phase ones etc...
>
yeah, I''ve noticed that in foreman too, and we keep both report
creation
time, and the client time, if they are off, we actually display a message
telling the user that the time is not in sync.

Ohad
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On 13 May 2011 18:46, Patrick <kc7zzv@gmail.com> wrote:
>
> On May 13, 2011, at 8:36 AM, Chris Phillips wrote:
>
> > Why would you ever want to trust a time stamp from the client instead
of
> just using your own time as you receive the report?
>
> In my case, when I run the import rake task, it imports stored reports that
> might be old.  This means that the time the report is imported into the
> server is wrong and the time inside the report is correct.  I also hope
that
> someday puppet will have a system that can automatically queue reports that
> can''t be sent and automatically send them later, though
I''ll admit I haven''t
> even cared enough to file a bug report.  If this happens, you''d
again want
> to trust the client''s time instead of the server''s time.
>
>
> If the system clock was wrong, I''m surprised SSL worked.
>
well the certs already existed, so there was no chance of a Valid Before
issue.
>
> If the timezone was different, I''d suggest filing a bug report
related to
> puppet not using the timezone properly.

The root cause... well... root reason... is timezone related, utc vs system
clock on the ESX host, however whilst there is wonky stuff, this is not a
scenario where it could be said that that should be fixed and Puppet
shouldn''t be blamed. I had a report on Dashboard dated "2011-05-13
18:05
BST" when it was actually run at 16:05 BST. Once NTP settles down
it''s a non
issue.

So Bug it is, just wanted a little feedback before I logged it.

Thanks

Chris

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.