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 926891[details]
Screenshot
Description of problem: I have a new install of Satellite 6 Beta, I have manually synchronised a repository, and now added it to a synchronisation plan. In the sync status page it shows:
content -> sync status -> Sync complete.
In the content -> sync plan -> products tab -> Never synced
So I assume the status is that the schedule has never run, yet the repo is synchronised.
Version-Release number of selected component (if applicable):
How reproducible: each time
Steps to Reproduce:
1. create a new repo (using RH ones)
2. Manually synchronise it
3. Create a sync plan
4. Add repo to sync plan
Actual results: also included command line:
[root@cmilsted-rhel6 ~]# hammer repository info --name "Red Hat Enterprise Linux 7 Server RPMs x86_64 7.0" --organization BSkyB
ID: 1
Name: Red Hat Enterprise Linux 7 Server RPMs x86_64 7.0
Label: Red_Hat_Enterprise_Linux_7_Server_RPMs_x86_64_7_0
Organization: BSkyB
Red Hat Repository: yes
Content Type: yum
URL: https://cdn.redhat.com/content/dist/rhel/server/7/7.0/x86_64/os
Publish Via HTTP: no
Published At: https://cmilsted-rhel6.saleslab.fab.redhat.com/pulp/repos/SkyBroadcast/Library/content/dist/rhel/server/7/7.0/x86_64/os
Product:
ID: 88
Name: Red Hat Enterprise Linux Server
GPG Key:
Sync:
Status: Finished
Last Sync Date: 2014/08/14 20:03:19
Created: 2014/08/14 10:37:43
Updated: 2014/08/14 10:37:43
Content Counts:
Packages: 4629
Package Groups: 70
Errata: 59
[root@cmilsted-rhel6 ~]# hammer sync-plan info --name "Weekly" --organization BSkyB
ID: 2
Name: Weekly
Start Date: 2014/08/14 19:00:51
Interval: weekly
Description: Weekly sync
Created at: 2014/08/14 19:00:12
Updated at: 2014/08/14 19:00:12
Also screenshot attached to show this.
Expected results:
Should show as manually synchronised or just synchronised.
Additional info:
Comment 1RHEL Program Management
2014-08-14 19:33:12 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 3sthirugn@redhat.com
2014-08-14 19:53:24 UTC
Sync plan now shows repo's last sync time in Sat6 build GA Snap 5 -
GA Snap 5 - Satellite-6.0.4-RHEL-6-20140813.2 (see screenshot)
Comment 4sthirugn@redhat.com
2014-08-14 19:53:49 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/8924 has been closed
-------------
Walden Raines
Applied in changeset commit:katello|56bb674f7686d4d43f126e2df539353e399165e5.
Comment 14sthirugn@redhat.com
2015-03-17 15:21:35 UTC
Verified.
Test steps:
1. create a new repo (using RH ones)
2. Manually synchronise it
3. Create a sync plan
4. Add repo to sync plan
5. Now the sync status shows the last synced status (see screenshot)
Version Tested:
Satellite-6.1.0-RHEL-6-20150311.1
Comment 15sthirugn@redhat.com
2015-03-17 15:22:05 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2015:1592