Chapter 9. Create and Synchronize a Red Hat Repository
9.1. Create a Repository
On the Red Hat Update Appliance (RHUA), log in to the Red Hat Update Infrastructure Management Tool.
[root@rhua ~]# rhui-manager
In the Red Hat Update Infrastructure Management Tool home screen, press
rto select manage repositories.-= Red Hat Update Infrastructure Management Tool =- -= Home =- r manage repositories c manage content delivery servers (CDS) l manage HAProxy load-balancer instances s synchronization status and scheduling e create entitlement certificates and client configuration RPMs n manage Red Hat entitlement certificates sm manage Red Hat subscriptions u manage RHUI users Connected: rhua.example.comPress
ato select add a new Red Hat content repository.---------------------------------------------------------------------------------- -= Red Hat Update Infrastructure Management Tool =- = Repository Management =- l list repositories currently managed by the RHUI i display detailed information on a repository a add a new Red Hat content repository c create a new custom repository (RPM content only) d delete a repository from the RHUI u upload content to a custom repository (RPM content only) p list packages in a repository (RPM content only) Connected: rhua.example.com ------------------------------------------------------------------------------ rhui (repo) => aWait for the Red Hat Update Infrastructure Management Tool to determine the entitled repositories. This might take several minutes.
Connected: rhua.example.com ------------------------------------------------------------------------------ rhui (repo) => a Loading latest entitled products from Red Hat... Determining undeployed products...
The Red Hat Update Infrastructure Management Tool prompts for a selection method.
... product list calculated Import Repositories: 1 - All in Certificate 2 - By Product 3 - By Repository Enter value (1-3) or 'b' to abort:
-
Press
2to select the By Product method. - Add Red Hat repositories to the RHUA by entering the number beside each repository that you want to include. The only repositories that will display are Red Hat repositories that are included in your entitlement certificate but have not yet been added.
-
Press
cwhen your are finished selecting the repositories. The Red Hat Update Infrastructure Management Tool displays the repositories to be deployed and prompts for confirmation. -
Press
yto proceed. A screen message indicates each successful deployment. -
Check that the correct repositories have been installed by pressing
lto access the list repositories currently managed by the RHUI screen.
9.2. Synchronize a Repository
The initial synchronization of Red Hat content can take a while, typically 10 to 20 minutes. Begin synchronizing as soon as possible.
Navigate to the Red Hat Update Infrastructure Management Tool home screen.
[root@rhua ~]# rhui-manager
Press
sto select synchronization status and scheduling.-= Red Hat Update Infrastructure Management Tool =- -= Home =- r manage repositories c manage content delivery servers (CDS) l manage HAProxy load-balancer instances s synchronization status and scheduling e create entitlement certificates and client configuration RPMs n manage Red Hat entitlement certificates sm manage Red Hat subscriptions u manage RHUI users Connected: rhua.example.comPress
srto select sync an individual repository immediately.------------------------------------------------------------------------------ -= Red Hat Update Infrastructure Management Tool =- -= Synchronization Status =- dr display repo sync summary vr view the details of the last repository sync sr sync an individual repository immediately Connected: rhua.example.com -------------------------------------------------------------------------------
Select the repository and press
cto confirm. -
Press
yto proceed. Enter
drto select display repo sync summary.------------------------------------------------------------------------------ rhui (sync) => dr ------------------------------------------------------------------------------ -= Red Hat Update Infrastructure Management Tool =- -= Repository Synchronization Status =- Last Refreshed: 13:59:27 (updated every 5 seconds, ctrl+c to exit) Next Sync Last Sync Last Result ------------------------------------------------------------------------------ Red Hat Enterprise Linux 7 Server - Extras from RHUI (RPMs) (x86_64) 02-29-2016 19:54 02-29-2016 13:59 Success Connected: rhua.example.com ------------------------------------------------------------------------------
9.3. Check Repository Synchronization
Run the following command to check whether a repository is being synchronized.
[root@rhua ~]# rhui-manager status
If you see a running job, as shown below, do not reboot. Wait until the result is something other than Running.
[root@rhua ~]# rhui-manager status Red Hat Enterprise Linux High Availability (for RHEL 6 Server) (RPMs) from RHUI (6Server-x86_64) Success Red Hat Enterprise Linux High Availability (for RHEL 7 Server) (RPMs) from RHUI (7Server-x86_64) Running
If you must reboot, or if the system was rebooted for a reason beyond your control, check the output of
rhui-manager statuswhen the system is up. You can also check the Pulp task list with the following command.[root@rhua ~]# pulp-admin -u admin -p admin tasks list
-
Use the actual password of the admin user after the
-pswitch. If you see No tasks found, then the synchronization process was safely interrupted. You can now synchronize the repository manually in rhui-manager, or you can wait for the next available time slot, during which the repository will synchronize automatically. Run
rhui-manager statusor the aforementioned pulp-admin command at any time to determine the status of the repository.Sometimes an attempt to synchronize a repository whose synchronization was interrupted can fail. The state is Running, and there is also a running Pulp task, but nothing is being transferred. If the status has been Running for an excessive amount of time, check whether there is an issue by examining the
repository synchronization status.Find out the name of the repository in the Pulp task list. For example,
[root@rhua ~]# pulp-admin -u admin -p admin tasks list +----------------------------------------------------------------------+ Tasks +----------------------------------------------------------------------+ Operations: sync Resources: rhel-x86_64-6-rhui-2-rpms-6Server-x86_64 (repository) State: Running Start Time: 2017-05-24T08:16:48Z Finish Time: Incomplete Task Id: 6e44a32d-2e11-41f2-bbe6-996531c5cda0 Operations: publish Resources: rhel-x86_64-6-rhui-2-rpms-6Server-x86_64 (repository) State: Waiting Start Time: Unstarted Finish Time: Incomplete Task Id: 13f5d531-2f0d-4a73-9d27-b4fd126b6f13Check the synchronization status. If you see the following output, there is a problem.
[root@rhua ~]# pulp-admin -u admin -p admin rpm repo sync status --repo-id rhel-x86_64-6-rhui-2-rpms-6Server-x86_64 +----------------------------------------------------------------------+ Repository Status [rhel-x86_64-6-rhui-2-rpms-6Server-x86_64] +----------------------------------------------------------------------+ This command may be exited via ctrl+c without affecting the request. Downloading metadata... [-] ... completed Downloading repository content... [-] [==================================================] 100% RPMs: 0/0 items Delta RPMs: 0/0 items ... completed Downloading distribution files... [==================================================] 100% Distributions: 0/0 items ... completed Importing errata... [-] ... completed Importing package groups/categories... [-] ... completed Cleaning duplicate packages... [-] ... completedYou have to cancel the open Pulp tasks and try synchronizing the affected repository again to resolve the problem and ensure that the repository is available on the RHUA. Use pulp-admin again as follows to view the task IDs.
[root@rhua ~]# pulp-admin -u admin -p admin tasks list +----------------------------------------------------------------------+ Tasks +----------------------------------------------------------------------+ Operations: sync Resources: rhel-x86_64-6-rhui-2-rpms-6Server-x86_64 (repository) State: Running Start Time: 2017-05-24T08:16:48Z Finish Time: Incomplete Task Id: 6e44a32d-2e11-41f2-bbe6-996531c5cda0 Operations: publish Resources: rhel-x86_64-6-rhui-2-rpms-6Server-x86_64 (repository) State: Waiting Start Time: Unstarted Finish Time: Incomplete Task Id: 13f5d531-2f0d-4a73-9d27-b4fd126b6f13Cancel the tasks.
[root@rhua ~]# pulp-admin -u admin -p admin tasks cancel --task-id 6e44a32d-2e11-41f2-bbe6-996531c5cda0 Task cancel is successfully initiated. [root@rhua ~]# pulp-admin -u admin -p admin tasks cancel --task-id 13f5d531-2f0d-4a73-9d27-b4fd126b6f13 Task cancel is successfully initiated.
-
Run
rhui-manager statusand verify that the status is Canceled. - Try synchronizing the repository again in rhui-manager. Use the same pulp-admin commands as earlier to monitor the progress. If you run into the same problem again, the repository is likely in an irreparable state and will have to be removed from RHUA and added again.
- View the Pulp task list to obtain the task IDs.
- Cancel the running and waiting tasks.
-
Use
rhui-managerto remove the repository. In edge cases, the repository cannot be removed because rhui-manager reports: "Task deletion is still occurring, any actions taken while this is not complete can result in errors." If that happens, restart the Pulp services.
For RHEL 6:
# service pulp_workers restart; service pulp_resource_manager restart; service pulp_celerybeat restart
For RHEL 7:
# systemctl restart pulp_workers; systemctl restart pulp_resource_manager; systemctl restart pulp_celerybeat
-
Replace
restartwithstatusin the above commands to verify each service has restarted. - Add the repository again in rhui-manager.
- Synchronize it immediately, or wait for the next automated synchronization.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.