Bug 1387543 - Changing sync plan frequency makes the start date invalid
Summary: Changing sync plan frequency makes the start date invalid
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Sync Plans
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium vote
Target Milestone: Unspecified
Assignee: Chris Roberts
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-21 08:48 UTC by Peter Ondrejka
Modified: 2017-07-05 08:49 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-11 18:37:02 UTC
Target Upstream Version:


Attachments (Terms of Use)
screenshot-syncplan.png (28.25 KB, image/png)
2016-10-21 08:48 UTC, Peter Ondrejka
no flags Details
production.log (38.37 KB, text/plain)
2016-10-21 08:49 UTC, Peter Ondrejka
no flags Details
sync plan set to hourly (100.58 KB, image/png)
2017-01-11 18:35 UTC, Chris Roberts
no flags Details
sync plan set to weekly without error (102.96 KB, image/png)
2017-01-11 18:36 UTC, Chris Roberts
no flags Details

Description Peter Ondrejka 2016-10-21 08:48:46 UTC
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.

Comment 1 Peter Ondrejka 2016-10-21 08:49:25 UTC
Created attachment 1212745 [details]
production.log

Comment 3 Brad Buckingham 2016-10-27 17:15:27 UTC
Note: attempted to reproduce this with upstream master and was unable to.

Comment 4 Chris Roberts 2017-01-11 18:35:53 UTC
Created attachment 1239572 [details]
sync plan set to hourly

Comment 5 Chris Roberts 2017-01-11 18:36:21 UTC
Created attachment 1239573 [details]
sync plan set to weekly without error

Comment 6 Chris Roberts 2017-01-11 18:37:02 UTC
Based on screenshots above in Katello 3.3 its working as intended marking as CLOSED UPSTREAM

- Chris Roberts


Note You need to log in before you can comment on or make changes to this bug.