Project

General

Profile

Bug #11295

sync plan dates saved incorrectly if I dont use the calendar widget

Added by Chris Peters almost 4 years ago. Updated 11 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1246262
Description of problem:
sync plan dates saved incorrectly if I dont use the calendar widget

Version-Release number of selected component (if applicable):
Sat 6.1 GA Snap 14

How reproducible:
Always

Steps to Reproduce:
1. Navigate to Content -> Sync Plans
2. Click 'New Sync Plan'
3. Enter name=syncplan1, description=test sync plan, Interval=hourly
4. Enter a future date example in YYYY-MM-DD format: 2015-10-01 (type this text in the text box and do not select from the calendar widget)
5. Leave Start Time with default (current time)

Actual results:
Sync plan is created with start date of 2015-09-30 (One day less than what I entered)

Expected results:
Sync plan should be created with a requested start date and not one day prior.

Additional info:
This same date works fine when I select the date from the calendar widget. This fails in QE automation for this same reason.

Associated revisions

Revision 5054658f (diff)
Added by Chris Peters almost 4 years ago

Fixes #11295 Sync dates compensate for timezone

To ensure the correct date is saved per the user's input
adjust the date to account for timezone difference

Revision efa0c539
Added by Walden Raines almost 4 years ago

Merge pull request #5400 from cpeters/11295-sync_date_saves_incorrectly

Fixes #11295 Sync dates compensate for timezone

History

#1 Updated by Chris Peters almost 4 years ago

  • Status changed from New to Assigned

#2 Updated by The Foreman Bot almost 4 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/5400 added
  • Pull request deleted ()

#3 Updated by Chris Peters almost 4 years ago

  • Assignee set to Chris Peters

#4 Updated by Eric Helms almost 4 years ago

  • Project changed from Bastion to Katello
  • Legacy Backlogs Release (now unused) set to 70
  • Triaged changed from No to Yes

#5 Updated by Chris Peters almost 4 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF