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.
Descriptionsandeep mutkule
2019-03-28 19:11:46 UTC
Description of problem:
When a product is part of a sync plan, "Next Sync" option for a repository in the product does not show the time when it is going to sync next. Status for "Next sync" always show the "Synced manually, no interval is set".
Version-Release number of selected component (if applicable):
Red Hat Satellite 6.4
How reproducible:
Steps to Reproduce:
1. Create a sync plan.
2. Add a repository to the sync plan.
3. Now Check the "Next Sync" status for the above repository.
Actual results:
"Next Sync" information mentions "Synced manually, no interval is set" when a product is part of a Sync Plan.
Expected results:
"Next sync" should display the next sync time.
Additional info:
Thanks for opening the bugzilla. This appears to be a duplicate of bug 1601951; therefore, closing this one. If you believe this is in error, please re-open with appropriate details. Thanks!
*** This bug has been marked as a duplicate of bug 1601951 ***