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.
Description of problem:
Trying to change sync-date (date&time of next sync tasks) of a sync plan, the change has no effect. While WebUI/TUI shows the sync plan has been updated properly, the products in the sync plan are still updated per original schedule.
Version-Release number of selected component (if applicable):
Satellite 6.0.6
How reproducible:
100%
Steps to Reproduce:
1. Create a hourly sync plan with some product added.
2. Wait the plan is executed for the 1st time.
3. Change sync-date (i.e. few minutes after the 1st execution, set sync date to current time plus few minutes, for fast reproducer). This can be done via:
hammer -u admin -p <password> sync-plan update --sync-date "YYYY-MM-DD HH:MM:SS" --id=<id>
4. Wait until the sync plan is scheduled again.
Actual results:
The synchronization will be executed 1 hour after the previous one, following the original schedule.
Expected results:
The synchronization should be executed per the changed time (i.e. within few minutes).
Additional info:
See relevant bz1177901.
*** Bug 1203125 has been marked as a duplicate of this bug. ***
Comment 9sthirugn@redhat.com
2015-05-01 21:29:14 UTC
Failed
1. Create a hourly sync plan with some product added.
- Created at 2015-05-01 16:08:00
- Scheduled to run at 2015-05-01 17:08:00
2. Wait the plan is executed for the 1st time. - Ran at 2015-05-01 17:08:00
3. Change sync-date (i.e. few minutes after the 1st execution, set sync date to current time plus few minutes, for fast reproducer). This can be done via:
# hammer> sync-plan update --id=1 --organization-id=1 --sync-date="2015-05-01 17:22:00"
4. Noticed that the sync job did not run at "2015-05-01 17:22:00"
Version Tested:
Satellite-6.1.0-RHEL-7-20150429.2