Pulp

We strongly recommend running all machines within a pulp deployment with the same timezone setting.

cristi.falcas@gmail.com wrote:

When using workers on different timezones we get this in the logs:

Substantial drift from resource_manager@v-is-puppet-03.synygy.net may mean clocks are out of sync. Current drift is
25199 seconds. [orig: 2015-03-17 06:48:33.819230 recv: 2015-03-16 23:48:34.387371]

To my knowledge, Pulp can't emit a log statements like these. Pulp also doesn't track clock drift. I think that your machines are drifting their time which is an issue unrelated to Pulp. Clock drift can cause problems in Pulp, but cannot be fixed by Pulp.

Maybe celery should support setting the correct timezone?

Celery is capable of using the timezone configured in the operating system, or having it set, but starting with Celery 3.0, UTC is used by default for all datetimes inside Celery. Pulp uses 3.1.11 currently. Pulp does not adjust this default. You can see how Pulp configures celery here. This means that Celery is using UTC so having machines in different timezones doesn't matter.

Pulp also does some datetime related things, but it also is supposed to use UTC throughout it. That seems unrelated to the issue as you've described it.

It shouldn't matter what timezone different compomnents are in. What really matters is that your computers know what time it is. Please synchronize your clocks and try to reproduce this issue. You can keep your components in different timezones if you want to test our support of that.

Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.