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.
Bug 1177908 - Changing sync-date for a sync plan has no effect
Summary: Changing sync-date for a sync plan has no effect
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.0.6
Hardware: All
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: Justin Sherrill
QA Contact: sthirugn@redhat.com
URL:
Whiteboard:
: 1203125 (view as bug list)
Depends On: 1139703
Blocks: 1122832
TreeView+ depends on / blocked
 
Reported: 2014-12-31 08:50 UTC by Pavel Moravec
Modified: 2021-04-06 18:02 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-12 13:57:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Sync plan verification screenshot (128.60 KB, image/png)
2015-05-21 20:12 UTC, sthirugn@redhat.com 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Pulp Redmine 922 0 High CLOSED - CURRENTRELEASE If a sync, publish, or consumer schedule is updated to change the time it runs, celerybeat does not run it at the new st... Never
Red Hat Bugzilla 1177904 0 medium CLOSED After removing a product from a sync plan, repos from the product are still synced according to the plan 2021-02-22 00:41:40 UTC

Internal Links: 1177904

Description Pavel Moravec 2014-12-31 08:50:53 UTC 
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.
Comment 2 Pavel Moravec 2014-12-31 09:40:57 UTC 
Potential workaround in katello-service restart does _not_ work. Products are still synchronized according to the old schedule.
Comment 3 Pavel Moravec 2014-12-31 11:21:40 UTC 
Maybe relevant: https://bugzilla.redhat.com/show_bug.cgi?id=1177904 (see the workaround there in https://bugzilla.redhat.com/show_bug.cgi?id=1177904#c3)
Comment 4 Pavel Moravec 2014-12-31 12:02:42 UTC 
Workaround: via hammer CLI, for one product after another, remove the (updated) sync plan from the product and add it back.
Comment 5 Justin Sherrill 2015-02-19 13:10:00 UTC 
This was resolved as part of  https://bugzilla.redhat.com/show_bug.cgi?id=1139703

Moving to POST
Comment 6 Justin Sherrill 2015-02-19 13:19:24 UTC 
actually, this is can be moved to on_qa
Comment 8 Pavel Moravec 2015-03-18 08:23:34 UTC 
*** Bug 1203125 has been marked as a duplicate of this bug. ***
Comment 9 sthirugn@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
Comment 10 Justin Sherrill 2015-05-14 14:18:26 UTC 
This is a known pulp issue https://pulp.plan.io/issues/922
Comment 11 pulp-infra@redhat.com 2015-05-14 14:24:36 UTC 
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
Comment 12 pulp-infra@redhat.com 2015-05-14 14:24:37 UTC 
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.
Comment 13 pulp-infra@redhat.com 2015-05-18 15:00:20 UTC 
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
Comment 14 pulp-infra@redhat.com 2015-05-18 17:30:24 UTC 
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 16 pulp-infra@redhat.com 2015-05-19 00:30:22 UTC 
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
Comment 17 pulp-infra@redhat.com 2015-05-20 16:00:25 UTC 
The Pulp upstream bug status is at VERIFIED. Updating the external tracker on this bug.
Comment 19 sthirugn@redhat.com 2015-05-21 20:12:08 UTC 
Verified in the same way as mentioned in Comment 9.  Sync worked fine this time.  Verification screenshot attached.

Version tested: Sat 6.1 GA Snap 5
Comment 21 Bryan Kearney 2015-08-11 13:21:09 UTC 
This bug is slated to be released with Satellite 6.1.
Comment 22 Bryan Kearney 2015-08-12 13:57:05 UTC 
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.
Comment 23 pulp-infra@redhat.com 2015-09-14 13:00:25 UTC 
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Note You need to log in before you can comment on or make changes to this bug.