Bug #35563
closed
sync time differs
Description
If i create a sync plan with a cron expression 40 8 * * * using my timezone +2 the next sync is planed at 10:40.
This should be adjusted, the sync actually happens at 08:40
Files
Updated by 
Updated by
Updated by Samir Jha 11 months ago
Hi Richard,
Can you verify if this is still an issue on any upgraded versions since 4.7 that this was opened against? I tried this on the UI and didn't see the issue.
Below is what the logs looked like for the sync plan creation call.
18:40:18 rails.1 | 2024-06-26T18:40:18 [I|app|29d0c6b2] Started POST "/katello/api/v2/organizations/1/sync_plans" for 192.168.121.1 at 2024-06-26 18:40:18 +0000
18:40:18 rails.1 | 2024-06-26T18:40:18 [I|app|29d0c6b2] Processing by Katello::Api::V2::SyncPlansController#create as HTML
18:40:18 rails.1 | 2024-06-26T18:40:18 [I|app|29d0c6b2] Parameters: {"interval"=>"custom cron", "startDate"=>"2024-06-26T18:39:25.893Z", "name"=>"test", "cron_expression"=>"45 14 * * *", "startTime"=>"2024-06-26T18:39:26.086Z", "sync_date"=>"Wed Jun 26 2024 14:39:00 GMT-0400 (Eastern Daylight Time)", "api_version"=>"v2", "organization_id"=>"1", "sync_plan"=>{"name"=>"test", "sync_date"=>"Wed Jun 26 2024 14:39:00 GMT-0400 (Eastern Daylight Time)", "interval"=>"custom cron", "cron_expression"=>"45 14 * * *"}}
Updated by Chris Roberts 10 months ago
- Status changed from Need more information to Closed
- Target version deleted (
Katello 4.11.2) - Triaged changed from No to Yes
Hi Richard,
If you are still having issues, please create a post on https://community.theforeman.org for further help. Closing this one out.