| Summary: | Changing sync plan frequency makes the start date invalid | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Peter Ondrejka <pondrejk> | ||||||||||
| Component: | Sync Plans | Assignee: | Chris Roberts <chrobert> | ||||||||||
| Status: | CLOSED UPSTREAM | QA Contact: | Katello QA List <katello-qa-list> | ||||||||||
| Severity: | medium | Docs Contact: | |||||||||||
| Priority: | medium | ||||||||||||
| Version: | 6.3.0 | CC: | bbuckingham, chrobert, jcallaha, oshtaier | ||||||||||
| Target Milestone: | Unspecified | Keywords: | Triaged | ||||||||||
| Target Release: | Unused | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2017-01-11 18:37:02 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: | |||||||||||
| Attachments: |
|
||||||||||||
Created attachment 1212745 [details]
production.log
Note: attempted to reproduce this with upstream master and was unable to. Created attachment 1239572 [details]
sync plan set to hourly
Created attachment 1239573 [details]
sync plan set to weekly without error
Based on screenshots above in Katello 3.3 its working as intended marking as CLOSED UPSTREAM - Chris Roberts |
Created attachment 1212744 [details] screenshot-syncplan.png Version-Release number of selected component (if applicable): Sat 6.3 snap 5 foreman-1.13.0-1.el7.noarch katello-3.2.0-2.rc2.el7.noarch Steps to Reproduce: 1. In UI (content > sync plans > new sync plan) 2. Create a hourly sync plan with start date sometime in future, save 3. View the new sync plan, edit the Interval field, select weekly from the drop-down list. Click save. 4. The Start Date field turns to "Invalid Date" and an error is displayed -- see screenshot attached. Next Sync field is not adjusted, unable to save. Expected results: Valid start date is unaffected after changing the sync plan interval, next sync is properly adjusted and the sync plan can be successfully saved with changed values. Additional info: Excrept from /var/log/foreman/production.log attached.