Bug 1465105
| Summary: | Note to update satellite-sync cron job to cdn-sync in upgrade docs provided by rhn-upgrade package | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite 5 | Reporter: | Candace Sheremeta <cshereme> | ||||
| Component: | Upgrades | Assignee: | Tomáš Kašpárek <tkasparek> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Ales Dujicek <adujicek> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 580 | CC: | adujicek, ggainey, shughes, tlestach, xdmoon | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | rhn-upgrade-5.8.0.28-1-sat | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-10-19 11:59:23 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1450111 | ||||||
| Attachments: |
|
||||||
|
Description
Candace Sheremeta
2017-06-26 16:32:46 UTC
Sat 5.7 User Guide really suggests to set up a cron job for periodic content synchronization: https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/5.7/html/User_Guide/chap-Automatically_Synchronizing_the_Red_Hat_Satellite_Server_Repository.html Based on this - yes - it makes sense to extend rhn-upgrade instructions with an extra note to update the cron job. Created attachment 1314591 [details]
0001-1465105-advise-users-to-change-cron-jobs-to-cdn-sync.patch
0001-1465105-advise-users-to-change-cron-jobs-to-cdn-sync.patch
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:2914 |