Description of problem: Currently it takes 24+ hours for the CDS to be able to deliver the content to the RHUI clients. This negatively impacts a customer's ability to get their systems secure. The CDN team has a goal to have the content available in CDN within 1 hour of the release of an errata. We should work on minimizing the time it takes to get the content to the CDS. We should consider: -A way for CDN to notify a RHUA to perform sync operations -A way for the CDS to sync content from the RHUA/CDS in a more efficient fashion.
This is significantly faster in rhui 3
(In reply to Chris Duryee from comment #3) > This is significantly faster in rhui 3 Could you please elaborate on that and describe how this RFE was implemented? I can see that the default repo_sync_frequency is still six hours, but do repos get synced asynchronously if they change and/or is the syncing more efficient now? How can this RFE be verified without waiting for an erratum to be shipped live and checking how fast it appears in the relevant repo in RHUI?
In RHUI 2, the process for the client to get an errata was as follows: * RHUA syncs content down * after its done, CDS syncs content down from RHUA * after that's done, client can update This process could take a long time, depending on how fast/slow the CDS sync is. In RHUI 3, step #2 is no longer needed. Once the RHUA syncs the content down, it should be available to the CDSes shortly after. To test this, you could probably just sync content to the RHUA, and then ensure clients are able to see it on a CDS.
Thanks, Chris. We've already verified repeatedly that synced content is (immediately) available. In addition, yesterday I deployed a RHUI environment with RHEL 5 repos. Later that day (US time, me already AFK) a critical async Firefox erratum went out (RHSA-2016:2843). This morning (European time) I see the new Firefox in my RHUI env, and my RHEL 5 client machine can fetch the package from there, too. According to rhui-manager, the repo was last synced 12-01-2016 22:49.
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/RHBA-2017:0367