Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
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.