Bug 1463696
Summary: | Incorrect Next Sync date calculation in weekly Sync Plan | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Peter Ondrejka <pondrejk> | ||||||
Component: | Content Management | Assignee: | Walden Raines <walden> | ||||||
Status: | CLOSED ERRATA | QA Contact: | Jitendra Yejare <jyejare> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 6.2.10 | CC: | bbuckingham, bkearney, jyejare, lpramuk, mruzicka, sthirugn, walden, zhunting | ||||||
Target Milestone: | 6.4.0 | Keywords: | Regression, Triaged | ||||||
Target Release: | Unused | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Linux | ||||||||
URL: | http://projects.theforeman.org/issues/16035 | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | 1302098 | Environment: | |||||||
Last Closed: | 2018-10-16 19:25:21 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Bug Depends On: | 1302098 | ||||||||
Bug Blocks: | 1396647, 1463301 | ||||||||
Attachments: |
|
Comment 1
Peter Ondrejka
2017-06-21 14:16:46 UTC
Created attachment 1290120 [details]
screenshot-syncplan
Upstream bug assigned to walden Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16035 has been resolved. See https://bugzilla.redhat.com/show_bug.cgi?id=1438845 for CEST related issue. Created attachment 1454655 [details]
[Verification] Screenshot Attached
Verified!
@ Satellite 6.4 snap 8.0
Steps:
Created sync plan 4 days(22nd June) before from now(26th June) with weekly sync interval.
Behavior:
The sync plan next sync date was calculated correctly from start date. In my case its 29th June.
[Verification] Screenshot Attached
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 |