Bug 1033839 - Synchronization Schedule ran but status displays 0 Bytes
Summary: Synchronization Schedule ran but status displays 0 Bytes
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs Install Guide
Version: Nightly
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: Unspecified
Assignee: Athene Chan
QA Contact: Dan Macpherson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-23 16:52 UTC by paul
Modified: 2019-09-25 21:04 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Build Name: 14370, Installation Guide-6.0-1 Build Date: 11-11-2013 14:07:51 Topic ID: 9704-466995 [Latest]
Last Closed: 2014-06-19 01:33:21 UTC
Target Upstream Version:


Attachments (Terms of Use)
print screen of SYNC menu (268.67 KB, image/jpeg)
2013-11-28 23:59 UTC, paul
no flags Details

Description paul 2013-11-23 16:52:13 UTC
Title: Applying a Synchronization Schedule

Describe the issue:
New installation Sat 6 mdp2, Login to web, d/l installed manifest, enable repositories, setup sync/plan/schedule for next day at 1 & 3am. Sync's ran, 7 on 7 repos were successful, no errors recorded for 2 that failed. I ran a manual sync of the 2 that failed at 7am successfully.  When I look at the sync status all the selected repos show size(packages)column as 0 bytes(using both IE9 and Firefox) I checked my file systems and they show that I added 50G from the syncs.  The start time, Duration, and Result columns appear to be correct. The SIZE(PACKAGES) column should not be reporting "0 Bytes (0)".

Suggestions for improvement:


Additional information:

Comment 1 RHEL Program Management 2013-11-23 17:01:04 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 3 paul 2013-11-24 22:53:18 UTC
I have removed a few and added several more repositories and now see that the only time the size(packages) is non zero is when you are performing a 'synchronize now' operation.

Comment 4 Athene Chan 2013-11-28 23:02:59 UTC
Hi Paul,

1. Logged into the Customer Portal
2. Downloaded the Manifest
3. Enabled Repositories -> Content > Repositories. Clicked on enable checkbox on each repo.
4. Setup Sync plan.
5. Sync ran and failed. Manually synchronized.

Can you tell me how you manually synced the repository? (Is this through the Synchronize Now" button as per https://access.redhat.com/site/documentation/en-US/Red_Hat_Satellite/6.0/html/Installation_Guide/Synchronization_Status.html  or something else entirely?

I am asking for this information so we can ascertain whether this just needs a warning on the book or if there is something wrong in the application.

Thanks for reporting this and for helping us iron out the books/application.

Cheers,
Athene

Comment 5 paul 2013-11-28 23:59:30 UTC
Created attachment 830426 [details]
print screen of SYNC menu

Comment 6 paul 2013-11-29 00:02:07 UTC
I manually synced using the "Synchronize Now" button. Only when you do a manual sync in this fashon is the SIZE(PACKAGES) column used, otherwise it's always zero. See the sync.jpg I attached.

in other words, when you select a repo and click the synchronize now, rhe remote repo is queried for anything new that has to be updated.  If there are files to update, this size value is reported in the SIZE column and the download begins. (that's how I see it!)

I hope that helps!

Comment 7 Athene Chan 2013-11-29 01:08:30 UTC
Hi Paul,

Sounds about right! Thanks for the explanation! This is actually how it usually behaves. "Synchronize Now" should be the initial synchronization step before creating a sync plan. I might add a note on that in the documentation to make it clearer! 

Just so you are wondering, this documentation change will more than likely be added in the next release of the book which will be on the next release of Red Hat Satellite 6. 

Thanks for clarifying again, Paul!

Have a good day,
Athene

Comment 12 Athene Chan 2014-06-19 01:33:21 UTC
Hello Paul,

This will be incorporated to the new documentation suite. I will be closing this ticket as resolved.

Please feel free to reopen this ticket if you have concerns.

Thank you,
Athene


Note You need to log in before you can comment on or make changes to this bug.