Bug 1612100
Summary: | Sync Plan Date incorrectly set in Timezone | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Samir Jha <sajha> | ||||||
Component: | Sync Plans | Assignee: | Samir Jha <sajha> | ||||||
Status: | CLOSED ERRATA | QA Contact: | Jameer Pathan <jpathan> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 6.3.0 | CC: | egolov, jpathan, mverma | ||||||
Target Milestone: | 6.4.0 | Keywords: | Triaged | ||||||
Target Release: | Unused | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | tfm-rubygem-katello-3.7.0.28-1 | Doc Type: | If docs needed, set a value | ||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2018-10-16 18:57:00 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Samir Jha
2018-08-03 13:26:52 UTC
Created from redmine issue http://projects.theforeman.org/issues/24519 Upstream bug assigned to None Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/24519 has been resolved. *** Bug 1625699 has been marked as a duplicate of this bug. *** Verified @satellite 6.4.0 snap 22 Steps: 1. go to Content > Sync Plans 2. Create Sync Plan 3. enter date and time for the new sync plan 4. save the sync plan Observation: The saved sync plan has same time and date as what was set by the user. Created attachment 1483967 [details]
before saving sync plan
Created attachment 1483968 [details]
after saving sync plan
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:2927 |