Technical Notes
Red Hat Update Infrastructure 2.1
Errata for Red Hat Update Infrastructure
Abstract
Errata for Red Hat Update Infrastructure.
Chapter 1. RHEA-2012:1205 - Red Hat Update Infrastructure 2.1 enhancement update
Buglist for RHEA-2012:13535-01 - Red Hat Update Infrastructure 2.1 enhancement update
- BZ#704630
- The pulp command line's authentication process has changed and now requires credentials for all system calls. As a consequence, a ping check before a login attempt does not work due to the lack of credentials. This fix allows ping attempts without authentication. The pulp command line now successfully pings before a login attempt.
- BZ#752969
- Previously, there was no package download status on the repository synchronization status screen. This update adds package download status to the repository synchronization status screen.
- BZ#788574
- A qpidd AVC denial was present in the SELinux audit log. This update uses a new version of qpidd with updated SELinux policy, which fixes the denial.
- BZ#789994
- Users manually included the Red Hat Update Appliance (RHUA) hostname into the configuration files. This update automates this step and the procedure is no longer required. It has been removed from the Package Installation chapter of the Red Hat Update Infrastructure Installation Guide.
- BZ#794855
- Previously, Client Entitlement required an extra procedural step for CA Certificates setup. The new update has automated the procedure and the step has been removed from the Client Entitlements chapter of the Red Hat Update Infrastructure Administration Guide.
- BZ#796139
- Deleting 20 or more multiple repositories simultaneously caused a traceback error to occur. This update uses new version of pulp that fixes these traceback errors.
- BZ#798281
- When executing
service pulp-cds status
, syntax usage errors appeared. This update adds a status call to thepulp-cds
init script.service pulp-cds status
now outputs the correct status message. - BZ#801113
- Deleting repositories from the Red Hat Update Appliance (RHUA) did not remove the repository content from associated Content Delivery Servers (CDSs). This update now correctly removes repository contents from CDSs when those repositories are deleted on the RHUA.
- BZ#802547
- Deleting repositories made
yum
unable to execute the client configuration RPM Packages in those directories. This update adds a note to the Red Hat Update Infrastructure Administration Guide regarding this issue. - BZ#803377
- A restrictive base OID of Red Hat Enterprise Linux (RHEL) products caused unexpected OID error messages reported against Red Hat content. This update corrects the checking mechanism to match RHEL product prefixes.
- BZ#803379
- All configuration files required manual configuration of the fully qualified domain name (FQDN) of the Red Hat Update Appliance (RHUA). The updated version of the rhui-installer produces a config RPM Package that updates the appropriate configuration files with the RHUA hostname.
- BZ#808351
- Running
rhui-manager status
during a connection failure causes an uncaught exception. As a consequence,rhui-manager status
reports a traceback error instead of a status message. This fix adds an exception that prints the following error message if communication is unavailable:Network error while connecting to the RHUA, please check the server is running and available
Network error while connecting to the RHUA, please check the server is running and available
Copy to Clipboard Copied! rhui-manager status
now runs successfully without any traceback error. - BZ#808965
- In the Red Hat Update Infrastructure Installation Guide, no description existed for adding a new CDS after RHUI deployment. This fix adds a note with a cross-link to the procedure for adding new CDS, which provides users with the necessary documentation.
- BZ#808966
- Procedure 2.3 of the Red Hat Update Infrastructure (RHUI) Installation Guide contained a step requiring manual modification of
/etc/pulp/cds.conf
when installing a CDS. This step is redundant;/etc/pulp/cds.conf
does not require manual modification. This change removes the step from the documentation. - BZ#809810
- Users could add repositories while products were out of sync. This caused an incorrect listing of repositories during new entitlement creation. This fix checks for add repository failure, reports an error and repopulates the list of available products. This displays a correct listing of repositories for new entitlement creation.
- BZ#810448
- The spec file for
pulp-0.0.263-18
contained a faulty line in the post-installation scriptlet. This caused pulp installation to report an access error for a missing file. This issue is fixed inpulp-0.0.263-25
. The faulty line has been removed and no errors appear during installation. - BZ#810691
- The Red Hat Update Infrastrucutre Installation Guide was missing a chapter for updating an expired entitlement-signing certificate. This update adds a new chapter to the guide. Users now update expired entitlement-signing certificate with Chapter 6. Identity Certificates.
- BZ#811792
- The
sha1
checksum is mandatory for Red Hat Enterprise Linux (RHEL) 5 guest repository access. RHEL 5 guests report an error during checksum if the user choosessha256
in Red Hat Update Appliance (RHUA). This update adds instructions to usesha1
for RHEL 5 and 6 guest access andsha256
for RHEL 6 only. This reduces the possibility of a user selectingsha256
for RHEL 5 access. - BZ#813072
- Red Hat Update Infrastructure (RHUI) uses an NSS database to secure QPID communication. NSS database generation was a user interactive process during rh-rhui-tools installation. This update automates the NSS database generation and configuration with the
nss-db-gen script
during the rh-rhui-tools installation. - BZ#813074
- Red Hat Update Infrastructure (RHUI) installation scripts used depreciated commands for RPM Package installation on Red Hat Enterprise Linux (RHEL) 6. This update replaces the instances of depreciated commands with the recommend
yum install
command, which ensures successful installation on RHEL 6. - BZ#813172
- A backup chapter was missing from the Red Hat Update Infrastructure (RHUI) Administration Guide. No information on RHUI backup existed. This update adds Chapter 12. Backup and Restore to the guide and now users have the information to backup and restore RHUI.
- BZ#814163
- A caching issue caused rhui-manager to not list previously deleted repositories. A patch for
rh-rhui-tools 2.0.68
repopulates the list of available products when adding a repository fails in rhui-manager. This fixes the list discrepancy problem. - BZ#815656
- The Red Hat Update Infrastructure (RHUI) Installation Guide provided no checksum file links. Users could not download the associated checksums. This update to the guide provides a note with checksum file links. Users now download the checksum files using the links provided.
- BZ#816473
- SELinux enforced a denial for the httpd service on both Red Hat Update Appliance (RHUA) and Content Delivery Server (CDS) when upgrading RHUI. This update includes a note to stop the pulp-server service on RHUA and pulp-cds service on the CDS before upgrading. The avoids further denials on the httpd service.
- BZ#819886
- grinder required retry logic to avoid Akamai issues with retrieving repodata. This update adds a
@Retry
decorator to yum within grinder. This invokes retry loading whenever yum returns an exception error. - BZ#819985
- Contents were not removed from the Content Delivery Servr (CDS) after a repository is unassociated. Unassociated RPM Packages still existed at
/var/lib/pulp-cds/packages/
. This update patches thecdslib.py
script to remove unassociated RPM Packages. - BZ#821319
- For Red Hat Update Infrastructure (RHUI), a debug script was requested for gathering debug data. This script is now included with Red Hat Update Appliance (RHUA) at
/usr/share/rh-rhua/rhui-debug.py
, which the user runs as follows:python /usr/share/rh-rhua/rhui-debug.py
# python /usr/share/rh-rhua/rhui-debug.py
Copy to Clipboard Copied! This script collects debug data and returns pathways to the collected data. - BZ#822637
- rhui-manager returned a traceback error when it received invalid repository data. This update applies patches
render.py
andpackages.py
. rhui-manager now returns a detailed error if it receives invalid repository data. - BZ#824940
- rhui-installer only added proxy configuration to
pulp.conf
but not torhui-tools.conf
. This fixes patchesrhua.py
andanswers.py
to add the proxy configuration to bothpulp.conf
andrhui-tools.conf
files. - BZ#825011
- The RHUA configuration script added a trailing slash for the proxy URL paramater. This causes repository synchronization to fail. This fix removes the trailing slash and defines the correct proxy value to provide repository synchronization.
- BZ#826142
- The Red Hat Update Infrastructure (RHUI) Administration Guide lacked a table of rhui-manager status return codes. This update adds Table 10.1 to Chapter 10. Monitoring. Users refer to Table 10.1 for status code meanings.
- BZ#829923
- Content Delivery Server (CDS) Clusters contain new features such as listing and registering. This update adds new rhui-manager GUI screenshots to documentation.
- BZ#829924
- Content Delivery Server (CDS) Clusters contain a new feature that allows users to associate and unassociate repositories. This update adds new rhui-manager GUI screenshots to documentation.
- BZ#829926
- Client entitlement and RPM Package configuration contains new features. This update adds new rhui-manager GUI screenshots to documentation.
- BZ#830624
- Client entitlement RPM Packages filenames generated with rhui-manager contained
el6
. This gives the impression that the RPM Packages are only built for Red Hat Enterprise Linux (RHEL) 6 clients but the RPM Packages are built for both RHEL 5 and 6 clients. This fix removes theel6
abbreviation from the client entitlement RPM Package filesnames to prevent confusion. - BZ#831188
- Users were promted for the path to the server SSL certificate during client config RPM Package creation. The path is now added to
rhui-tools.conf
. Users are no longer prompted for this path during client config RPM Package creation. - BZ#831655
- The roles of load balancers were changed in RHUI 2.0. Information about installing load balancer in the Red Hat Update Infrastructure (RHUI) Installation Guide was outdated. This update adds the following note to the guide:
Each CDS serves as a load balancer. There is no need to install the load balancer on the Red Hat Update Appliance or a separate instance.
Each CDS serves as a load balancer. There is no need to install the load balancer on the Red Hat Update Appliance or a separate instance.
Copy to Clipboard Copied! - BZ#838583, BZ#838658
- rhui-manager used two separate repository lists to display and track the repositories selected during the creation of client entitlement certificate. This led to a conflict between items on both lists. This fix creates a repository list synchronises with repositories displayed to the user. This removes the conflict error.
- BZ#839718, BZ#840016
- The
install_RHUA.sh
andinstall_CDS.sh
scripts did not check if a fully qualified domain name (FQDN) was set. This causes an error during installation if hostname was incorrectly set. This update modifies the scripts to check if hostname is set before continuing. If hostname is set tolocalhost.localdomain
orlocalhost
, the scripts stop and report an error. - BZ#839726
- Installation of rh-rhui-tools requires both
install_RHUA.sh
andinstall_tools.sh
scripts. These two scripts were run as two separate steps. This update modifies theinstall_RHUA.sh
script to run theinstall_tools.sh
script automatically to reduce installation steps. - BZ#840005, BZ#840977
- Red Hat Update Infrastructure (RHUI) automatically associated all repositories with the first CDS cluster. This caused problems when asociating repositories with other CDS clusters. This fix removes the automatic association of repositiories to CDS clusters. All associations are performed manually in RHUI 2.1
- BZ#840979
- Matching names of packages in unprotected custom repositories and names of protected custom repositiories caused requests for packages in the unprotected repository to use the protected repository's certificate. This resulted in access errors. This update changes the mechanism for matching repository URLs with protected repositories and provides correct access to packages.
- BZ#842404
- Red Hat Update Infrastructure 2.1 no longer uses
ruby-gofer-0.64-1.el6.noarch.rpm
. This update removes this package from the Red Hat Update Infrastructure 2.1 ISOs. - BZ#842785
- A combination of valid and expired entitlements caused an unfiltered list of unprotected repositories during client configuration RPM creation. This caused client entitlement certificate generation to fail. This update filters the unprotected repositories associated with the chosen CDS cluster during client configuration RPM creation.
- BZ#842827
- Red Hat Update Infrastructure reported GPG errors when accessing content in a custom repository due to incorrect GPG signatures. This update adds the ability to sign content in a custom repository with Red Hat's public GPG key or a a custom GPG key.
- BZ#842859
- Updates from Red Hat Update Infrastructure (RHUI) 2.0.3 required users to manually add the
ssl_ca_cert
in/etc/rhui/rhui-tools.conf
. This update adds thessl_ca_cert
configuration option to/etc/rhui/rhui-tools.conf
if it is not present already. - BZ#844718
- Earlier versions of Red Hat Update Infrastructure (RHUI) user interface displayed the following message in the entitlement certificate generation screen:This update removes this message as it is no longer applicable to RHUI 2.1.
* indicates the repositories deployed on RHUI
* indicates the repositories deployed on RHUI
Copy to Clipboard Copied! - BZ#846386
- Creation of a client configuration RPM from custom protected and unprotected repositories caused rhui-manager to generate an error. This issue has been fixed in Red Hat Update Infrastructure (RHUI) 2.1.
Chapter 2. RHEA-2012:1218 - Red Hat Update Infrastructure 2.1 bug fix update
This update provides users with instructions on database migration to the latest version. Users are advised to run the following commands after installing packages for RHUI 2.1:
pulp-migrate service pulp-server restart
# pulp-migrate
database migration to version 41 complete
# service pulp-server restart
Stopping httpd: [ OK ]
Stopping Qpid AMQP daemon: [ OK ]
Stopping mongod: [ OK ]
Starting mongod: [ OK ]
Starting Qpid AMQP daemon: [ OK ]
Starting httpd: [ OK ]
Note
This process takes up to one hour to complete.
Buglist for RHEA-2012:1218 - Red Hat Update Infrastructure 2.1 bug fix update
- BZ#851888
- This update adds instructions for running the
pulp-migrate
command as part of the RHUI 2.1 upgrade process. Users can find these instructions in the README file on the RHUI 2.1 ISO. - BZ#852105
- This update adds an important note on downloading the RHUI ISO for customers with an existing content certificate. Customers who already have a content certificate need to either regenerate their content certificate or use the following URL:
https://cdn.redhat.com/content/dist/rhel/rhui/server/6/6Server/x86_64/rhui/2.0/iso/RHEL-6-RHUI-2-LATEST-Server-x86_64-DVD.iso
These instructions now appear in the README file on the RHUI 2.1 ISO. - BZ#852110
- The Red Hat Update Infrastructure 2.1 Installation Guide contained old checksum URLs in Procedure 2.2. Installing the Red Hat Update Infrastructure packages on the Red Hat Update Appliance Server. This update provides the correct checksum URLs to this procedure.
Chapter 3. RHBA-2013:0571 - Red Hat Update Infrastructure 2.1.1 bug fix update
CDS
- BZ#892394
On systems with a non-default umask, goferd may create files that are inaccessible to other components of RHUI. This fix updates goferd and sets its umask to 022 so CDS content is accessible via pulp-cds.
On systems with a non-default umask, goferd may create files that are inaccessible to other components of RHUI. This fix updates goferd and sets its umask to 022 so CDS content is accessible via pulp-cds.
Copy to Clipboard Copied!
RHUA
- BZ#862016
Proxy settings weren't parsed in the rhui-tools configuration file and caused content synchronization to fail. This fix adds in [redhat] section to rhui-tools.conf so that the proxy setting are parsed without errors.
Proxy settings weren't parsed in the rhui-tools configuration file and caused content synchronization to fail. This fix adds in [redhat] section to rhui-tools.conf so that the proxy setting are parsed without errors.
Copy to Clipboard Copied! - BZ#871497
There was a typo in rhui-manager. This fix corrects the typo in cds.py.
There was a typo in rhui-manager. This fix corrects the typo in cds.py.
Copy to Clipboard Copied! - BZ#833007
When clients tried to access CDS servers where none were accessible, the system will try to connect to a https://None/. This bug updates rhui-lb.py so that an appropriate error message displays.
When clients tried to access CDS servers where none were accessible, the system will try to connect to a https://None/. This bug updates rhui-lb.py so that an appropriate error message displays.
Copy to Clipboard Copied! - BZ#845941
Creating two or more repository paths with the same prefix returned an error. This bug fix corrects how Red Hat Update Appliance checks the repository paths and allows repository paths to share the same prefix.
Creating two or more repository paths with the same prefix returned an error. This bug fix corrects how Red Hat Update Appliance checks the repository paths and allows repository paths to share the same prefix.
Copy to Clipboard Copied! - BZ#815975
When upgrading RHUI from 2.0.1 to 2.0.3, custom repositories resulted in mismatch errors from the client certificate and the repository CA certificate, blocking access to the custom repositories. This is caused by the regex used in creating custom repositories only using subarchitectures in the last part of the directory path. This patch prevents entitlement path guessing if there are different architectures involved. Custom repositories are now accessible after upgrades.
When upgrading RHUI from 2.0.1 to 2.0.3, custom repositories resulted in mismatch errors from the client certificate and the repository CA certificate, blocking access to the custom repositories. This is caused by the regex used in creating custom repositories only using subarchitectures in the last part of the directory path. This patch prevents entitlement path guessing if there are different architectures involved. Custom repositories are now accessible after upgrades.
Copy to Clipboard Copied! - BZ#876423
Incorrect parsing logic removed valid data from entitlement certificate's OID values and caused the import of entitlement certificates to fail with traceback errors. This patch prevents the removal of valid data. Certificates now import without issue.
Incorrect parsing logic removed valid data from entitlement certificate's OID values and caused the import of entitlement certificates to fail with traceback errors. This patch prevents the removal of valid data. Certificates now import without issue.
Copy to Clipboard Copied! - BZ#848885
Modifications in answers file were not propagated to the configurations files: rhui-tools.conf and pulp.conf. This fix updates rhui_configurator.py, answers.py, and rhua.py. rhui-installer now propagates all answers file modifications.
Modifications in answers file were not propagated to the configurations files: rhui-tools.conf and pulp.conf. This fix updates rhui_configurator.py, answers.py, and rhua.py. rhui-installer now propagates all answers file modifications.
Copy to Clipboard Copied! - BZ#856637
The nss-db-gen script generated certificates that are valid for only 12 months. This bug fix updates the script and changes the default validity from 12 months to 48 months.
The nss-db-gen script generated certificates that are valid for only 12 months. This bug fix updates the script and changes the default validity from 12 months to 48 months.
Copy to Clipboard Copied! - BZ#847306
When trying to synchronize with an already deleted repository, rhui-manager returns an unhandled exception error. This bug fix updates pulp_api.py so "None" is returned when synchronizing with a non-existent repository.
When trying to synchronize with an already deleted repository, rhui-manager returns an unhandled exception error. This bug fix updates pulp_api.py so "None" is returned when synchronizing with a non-existent repository.
Copy to Clipboard Copied!
Security
- BZ#892488
World-readable permissions were set for pulp.conf and the pulp log file (/var/log/pulp). This enabled any user to view the two files and caused potential security issues. This bug fix changes the permissions so that other users do not have read permission.
World-readable permissions were set for pulp.conf and the pulp log file (/var/log/pulp). This enabled any user to view the two files and caused potential security issues. This bug fix changes the permissions so that other users do not have read permission.
Copy to Clipboard Copied!
Tools
- BZ#811796
Previously, yum displayed the unique numeric identifier for custom repositories. Repositories were not immediately identifiable because of this convention. The fix appends the custom repository name instead of the unique numeric identifier to the yum repository configuration.
Previously, yum displayed the unique numeric identifier for custom repositories. Repositories were not immediately identifiable because of this convention. The fix appends the custom repository name instead of the unique numeric identifier to the yum repository configuration.
Copy to Clipboard Copied! - BZ#867803
The rhui-debug script collected contents from /var/log/httpd and caused content duplication. The fix updates rhui-debug.py and removes the collection of files under /var/log/httpd.
The rhui-debug script collected contents from /var/log/httpd and caused content duplication. The fix updates rhui-debug.py and removes the collection of files under /var/log/httpd.
Copy to Clipboard Copied! - BZ#865822
When the wrong password is provided for the entitlement certificate CA, an unhandled exception error occurred in rhui-manager. This bug fix updates identity_cert.py and launcher.py. The error is handled and logged.
When the wrong password is provided for the entitlement certificate CA, an unhandled exception error occurred in rhui-manager. This bug fix updates identity_cert.py and launcher.py. The error is handled and logged.
Copy to Clipboard Copied! - BZ#860494
The package description for rh-rhui-tools requires expansion. This bug fix updates rh-rhui-tools.spec and includes a detailed description.
The package description for rh-rhui-tools requires expansion. This bug fix updates rh-rhui-tools.spec and includes a detailed description.
Copy to Clipboard Copied! - BZ#879546
Uploading a broken certificate to rhui-manager returned an unhandled trace back error. This fix updates cert.py so rhui-manager displays a proper error message.
Uploading a broken certificate to rhui-manager returned an unhandled trace back error. This fix updates cert.py so rhui-manager displays a proper error message.
Copy to Clipboard Copied! - BZ#902557
The rhui-lb plugin failed to support proxy servers and caused synchronization between the RHUA and CDS to fail. This fix adds proxy support to rhui-lb.py and provides successful synchronization.
The rhui-lb plugin failed to support proxy servers and caused synchronization between the RHUA and CDS to fail. This fix adds proxy support to rhui-lb.py and provides successful synchronization.
Copy to Clipboard Copied! - BZ#821319
A rhui-debug script was requested for gathering debug data. rhui-debug.py is now installed on Red Hat Update Appliance (RHUA) at rhui-debug.py. Run 'python /usr/share/rh-rhua/rhui-debug.py' to collect debug data; pathways to the collected data will also be returned.
A rhui-debug script was requested for gathering debug data. rhui-debug.py is now installed on Red Hat Update Appliance (RHUA) at rhui-debug.py. Run 'python /usr/share/rh-rhua/rhui-debug.py' to collect debug data; pathways to the collected data will also be returned.
Copy to Clipboard Copied! - BZ#847080
User certificate expirations in a non-interactive mode resulted in traceback errors. This patch adds exception handling into the RHUI CLI script to force the exception. It informs the user that the certificate has expired and rhui-manager needs to be restarted.
User certificate expirations in a non-interactive mode resulted in traceback errors. This patch adds exception handling into the RHUI CLI script to force the exception. It informs the user that the certificate has expired and rhui-manager needs to be restarted.
Copy to Clipboard Copied! - BZ#908639
When adding a new CDS and select abort, an error message returned. This fix updates cds.py so when abort action is performed, the shell interaction will end and return to the previous screen.
When adding a new CDS and select abort, an error message returned. This fix updates cds.py so when abort action is performed, the shell interaction will end and return to the previous screen.
Copy to Clipboard Copied! - BZ#910707
When upgrading RHUI to 2.1.1, rh-rhui-tools-debug-script was not installed on CDS. This fix updates pulp-cds to include the script.
When upgrading RHUI to 2.1.1, rh-rhui-tools-debug-script was not installed on CDS. This fix updates pulp-cds to include the script.
Copy to Clipboard Copied!
Chapter 4. RHBA-2013:0767 - Red Hat Update Infrastructure 2.1.2 bug fix update
CDS
- BZ#916308
During a synchronization, Red Hat Update Appliance returned different relative URLs than the ones in the CDS repository list and caused CDS to delete those repositories. This bug fix updates 'relative URL checking' in src/pulp/cds/cdslib.py so the correct relative URLs are returned.
During a synchronization, Red Hat Update Appliance returned different relative URLs than the ones in the CDS repository list and caused CDS to delete those repositories. This bug fix updates 'relative URL checking' in src/pulp/cds/cdslib.py so the correct relative URLs are returned.
Copy to Clipboard Copied!
RHUA
- BZ#916326
Synchronization of two repositories with similar content signed with different GPG keys caused a conflict between two of the same packages with the same checksum prefix. This fix changes the behaviour to use the full checksum instead of the prefix when creating the the package URL, which provides successful synchronization.
Synchronization of two repositories with similar content signed with different GPG keys caused a conflict between two of the same packages with the same checksum prefix. This fix changes the behaviour to use the full checksum instead of the prefix when creating the the package URL, which provides successful synchronization.
Copy to Clipboard Copied! - BZ#916378
Previously, rhui-manager removed repositories from the repository list but did not delete the associated packages on Red Hat Update Appliance and CDS instances. This bug fix provides a cleanup script to remove all orphaned packages to reclaim disk space.
Previously, rhui-manager removed repositories from the repository list but did not delete the associated packages on Red Hat Update Appliance and CDS instances. This bug fix provides a cleanup script to remove all orphaned packages to reclaim disk space.
Copy to Clipboard Copied!
Tools
- BZ#952300
The lack of _default_grabopts in older versions of yum rendered the RHUI client configuration RPMs incompatible with RHEL 5. This fix defines the default grabopts directly for an AttributeError exception. The client configuration RPMs are now compatible
The lack of _default_grabopts in older versions of yum rendered the RHUI client configuration RPMs incompatible with RHEL 5. This fix defines the default grabopts directly for an AttributeError exception. The client configuration RPMs are now compatible
Copy to Clipboard Copied!
Documentation
- BZ#921250
When updating Red Hat Update Infrastructure to 2.1.2, a migration script needs to be run to avoid package conflicts. This bug fix updates the Administration Guide to include technical materials on the migration script.
When updating Red Hat Update Infrastructure to 2.1.2, a migration script needs to be run to avoid package conflicts. This bug fix updates the Administration Guide to include technical materials on the migration script.
Copy to Clipboard Copied!
Documentation-Administration_Guide
- BZ#924783
New technical material on the 'pulp-purge-packages' script was required. This update adds Chapter 13. Deleting Orphaned Packages in the Red Hat Update Infrastructure Administration Guide.
New technical material on the 'pulp-purge-packages' script was required. This update adds Chapter 13. Deleting Orphaned Packages in the Red Hat Update Infrastructure Administration Guide.
Copy to Clipboard Copied! - BZ#908405
In the Red Hat Update Infrastructure Administration Guide, a step for data-base migration was needed. This bug fix adds the 'pulp-migrate' command in Procedure 12.1.
In the Red Hat Update Infrastructure Administration Guide, a step for data-base migration was needed. This bug fix adds the 'pulp-migrate' command in Procedure 12.1.
Copy to Clipboard Copied! - BZ#908135
In the documentation, there were inconsistent use of command prompts ('$' or '#'). This bug fix updates the Installation Guide and Administration Guide to use '#' (superuser) throughout the documentation.
In the documentation, there were inconsistent use of command prompts ('$' or '#'). This bug fix updates the Installation Guide and Administration Guide to use '#' (superuser) throughout the documentation.
Copy to Clipboard Copied!
Documentation-Installation_Guide
- BZ#921848
Entitlement screen shots and instructions were outdated in the Red Hat Update Infrastructure Installation Guide. This bug fix updates section 2.2 to include the latest screen shots and instructions.
Entitlement screen shots and instructions were outdated in the Red Hat Update Infrastructure Installation Guide. This bug fix updates section 2.2 to include the latest screen shots and instructions.
Copy to Clipboard Copied!
Chapter 5. RHBA-2013:16585 - Red Hat Update Infrastructure 2.1.3 bug fix update
CDS
- BZ#989506
This update adds the ability to limit the content that a Content Delivery Server can synchronize as it was not honoring the configuration option 'remove_old_versions.' This meant the customer was unable to remove older versions of packages from a Content Delivery Server. The Content Delivery Server synchronization has been updated to use similar options to those allowed by RHUA. These are 'num_old_packages' and 'remove_old_packages.' The Content Delivery Server is now able to limit the amount of content it synchronizes so that only the latest packages are retained.
This update adds the ability to limit the content that a Content Delivery Server can synchronize as it was not honoring the configuration option 'remove_old_versions.' This meant the customer was unable to remove older versions of packages from a Content Delivery Server. The Content Delivery Server synchronization has been updated to use similar options to those allowed by RHUA. These are 'num_old_packages' and 'remove_old_packages.' The Content Delivery Server is now able to limit the amount of content it synchronizes so that only the latest packages are retained.
Copy to Clipboard Copied! - BZ#996198
This update changes the behavior of a Content Delivery Server synchronization to allow a limit on the synchronization of older packages. The RHUA now sends two synchronization options to the Content Delivery Server when making a synchronization call. This allows the Content Delivery Server to match the behavior of the RHUA. Two configuration options have been added to the Content Delivery Server configuration to allow the Content Delivery Server to override options from the RHUA and further restrict how many older packages will be synchronized. This prevents errors on a RHUA when the RHUA is limiting older packages but the Content Delivery Server was unaware. The RHUA and Content Delivery Server are now more closely related in behavior. Additionally a Content Delivery Server now has the option to further reduce file storage requirements by only synchronizing the latest version of a package.
This update changes the behavior of a Content Delivery Server synchronization to allow a limit on the synchronization of older packages. The RHUA now sends two synchronization options to the Content Delivery Server when making a synchronization call. This allows the Content Delivery Server to match the behavior of the RHUA. Two configuration options have been added to the Content Delivery Server configuration to allow the Content Delivery Server to override options from the RHUA and further restrict how many older packages will be synchronized. This prevents errors on a RHUA when the RHUA is limiting older packages but the Content Delivery Server was unaware. The RHUA and Content Delivery Server are now more closely related in behavior. Additionally a Content Delivery Server now has the option to further reduce file storage requirements by only synchronizing the latest version of a package.
Copy to Clipboard Copied! - BZ#952912
This update fixes when the logic on a Content Delivery Server was not accounting for deleting an empty directory. This meant that empty directories from a repository deleted on a Content Delivery Server were not being cleaned up. Logic has been added to check for the top level repository directory and remove it if it is empty after a repository has been deleted. This means that deleting a repository is cleaner and the empty directories are removed.
This update fixes when the logic on a Content Delivery Server was not accounting for deleting an empty directory. This meant that empty directories from a repository deleted on a Content Delivery Server were not being cleaned up. Logic has been added to check for the top level repository directory and remove it if it is empty after a repository has been deleted. This means that deleting a repository is cleaner and the empty directories are removed.
Copy to Clipboard Copied! - BZ#1024975
This update fixes issues with cleaning up some pieces of data when deleting a repository on a Content Delivery Server. This caused the pulp-purge-packages script to not know these packages were deleted and meant that the orphaned packages were unable to be removed. The data when deleting a repository on a Content Delivery Server is now correctly removed.
This update fixes issues with cleaning up some pieces of data when deleting a repository on a Content Delivery Server. This caused the pulp-purge-packages script to not know these packages were deleted and meant that the orphaned packages were unable to be removed. The data when deleting a repository on a Content Delivery Server is now correctly removed.
Copy to Clipboard Copied! - BZ#1017310
This update adds a way to control the logging output for a CDS, which helps with debugging. Users can now observe the log file to see grinder's behaviour. New logging options also provide fine grained control, logging for specific modules, and alter so certain modules' output saves to a different file or is disabled.
This update adds a way to control the logging output for a CDS, which helps with debugging. Users can now observe the log file to see grinder's behaviour. New logging options also provide fine grained control, logging for specific modules, and alter so certain modules' output saves to a different file or is disabled.
Copy to Clipboard Copied!
RHUA
- BZ#830679
This update fixes the assumption that a certificate was invalid if the file name did not use the extension .pem. This resulted in valid certificates being marked as invalid. This has been changed so that an attempt is made with the certificate and it is only marked as invalid after it has failed. This means that a certificate with any extension can be used and the file name no longer needs to end in .pem.
This update fixes the assumption that a certificate was invalid if the file name did not use the extension .pem. This resulted in valid certificates being marked as invalid. This has been changed so that an attempt is made with the certificate and it is only marked as invalid after it has failed. This means that a certificate with any extension can be used and the file name no longer needs to end in .pem.
Copy to Clipboard Copied! - BZ#845258
This update fixes the detection of the difference between a repository having not been synchronized before or it having an error from the previous synchronization. This meant that a newly added repository would display as 'Error' in the synchronization history until its first synchronization was completed. The logic has been updated to account for a special case were the repository is new and it has no previous synchronization history. This change means the synchronization status is more accurate.
This update fixes the detection of the difference between a repository having not been synchronized before or it having an error from the previous synchronization. This meant that a newly added repository would display as 'Error' in the synchronization history until its first synchronization was completed. The logic has been updated to account for a special case were the repository is new and it has no previous synchronization history. This change means the synchronization status is more accurate.
Copy to Clipboard Copied! - BZ#971286
This update fixes a problem with Pulp not handling errata that spanned multiple repositories. This meant that the errata information was inaccurate. The code for RHUI has been modified to correct this problem. The errata information for errata spanning multiple repositories is now accurate.
This update fixes a problem with Pulp not handling errata that spanned multiple repositories. This meant that the errata information was inaccurate. The code for RHUI has been modified to correct this problem. The errata information for errata spanning multiple repositories is now accurate.
Copy to Clipboard Copied! - BZ#1016838
This update fixes an issue with grinder not updating the symbolic links when a different version is downloaded. This problem would become evident when two repositories were synchronized that shared the same package. On the remote source the file changes with a different checksum and the two repositories would be re-synchronize. The first repository will download the new file and update the symbolic link then the second repo would see that the file has been downloaded and not update the broken symbolic link. This meant the yum repository would end up serving the wrong contents for the file. A fix has been placed in the grinder logic to ensure it always looks at the symbolic link and updates it it when needed. This means that the yum repositories are now serving the correct file.
This update fixes an issue with grinder not updating the symbolic links when a different version is downloaded. This problem would become evident when two repositories were synchronized that shared the same package. On the remote source the file changes with a different checksum and the two repositories would be re-synchronize. The first repository will download the new file and update the symbolic link then the second repo would see that the file has been downloaded and not update the broken symbolic link. This meant the yum repository would end up serving the wrong contents for the file. A fix has been placed in the grinder logic to ensure it always looks at the symbolic link and updates it it when needed. This means that the yum repositories are now serving the correct file.
Copy to Clipboard Copied! - BZ#906371
This update fixes a Content Delivery Server not deleting associated certificates after a repository was deleted. This meant that the Content Delivery Server would have certificates for deleted repos under /etc/pki/pulp/content. The Content Delivery Server has been updated to delete the associated certificates upon repository deletion. This means that the Content Delivery Server will also remove the associated certificates.
This update fixes a Content Delivery Server not deleting associated certificates after a repository was deleted. This meant that the Content Delivery Server would have certificates for deleted repos under /etc/pki/pulp/content. The Content Delivery Server has been updated to delete the associated certificates upon repository deletion. This means that the Content Delivery Server will also remove the associated certificates.
Copy to Clipboard Copied! - BZ#1011082
This update fixes an issue where RHUI was sharing a directory with subscription-manager for certificates. When the subscription-manager deleted its own certificates it deleted everything in the directory causing the RHUI certificates to be deleted as well. The certificates are now placed in /etc/pki/rhui instead of /etc/pki/entitlement/ so that subscription-manager will no longer delete the RHUI certificates.
This update fixes an issue where RHUI was sharing a directory with subscription-manager for certificates. When the subscription-manager deleted its own certificates it deleted everything in the directory causing the RHUI certificates to be deleted as well. The certificates are now placed in /etc/pki/rhui instead of /etc/pki/entitlement/ so that subscription-manager will no longer delete the RHUI certificates.
Copy to Clipboard Copied! - BZ#1007662
This update extends the duration of the RHUI generated certificate /etc/pki/rhua/user-ca-cert.crt that was configured to expire after one year. This meant that a customer would need to regenerate the certificate one year after the date of installation. The life of the certificate has been extended to twenty years so that the customer will not need to regenerate the certificate every year.
This update extends the duration of the RHUI generated certificate /etc/pki/rhua/user-ca-cert.crt that was configured to expire after one year. This meant that a customer would need to regenerate the certificate one year after the date of installation. The life of the certificate has been extended to twenty years so that the customer will not need to regenerate the certificate every year.
Copy to Clipboard Copied! - BZ#957128
This update fixes a problem with not checking on the client side if the RPM files to be uploaded were valid. This meant that a bad rpm file could stop the entire upload when uploading multiple files. Now the client side is checked to ensure that the rpm file is valid. If it is not the invalid files will be skipped and the valid files will be uploaded. This means that the customer is able to upload a directory of rpm files and the valid files will be uploaded but bad files will be skipped.
This update fixes a problem with not checking on the client side if the RPM files to be uploaded were valid. This meant that a bad rpm file could stop the entire upload when uploading multiple files. Now the client side is checked to ensure that the rpm file is valid. If it is not the invalid files will be skipped and the valid files will be uploaded. This means that the customer is able to upload a directory of rpm files and the valid files will be uploaded but bad files will be skipped.
Copy to Clipboard Copied! - BZ#1024804
This update fixes confusing entries in the synchronization history when a repository is deleted then re-added. The way the last synchronization is calculated now accounts for when a repository was deleted. The synchronization status now displays 'Never' when a repository has been re-added after deletion.
This update fixes confusing entries in the synchronization history when a repository is deleted then re-added. The way the last synchronization is calculated now accounts for when a repository was deleted. The synchronization status now displays 'Never' when a repository has been re-added after deletion.
Copy to Clipboard Copied! - BZ#1030473
This update adds the ability for RHUA to read a Red Hat v3 entitlement certificate. Red Hat is moving to a 'v3' version of encoding entitlement data in a certificate because the 'v3' format allows more entitlement data to be stored. Customers are now able to input a Red Hat v1 or v3 entitlement certificate into RHUA and the entitlements will be read correctly.
This update adds the ability for RHUA to read a Red Hat v3 entitlement certificate. Red Hat is moving to a 'v3' version of encoding entitlement data in a certificate because the 'v3' format allows more entitlement data to be stored. Customers are now able to input a Red Hat v1 or v3 entitlement certificate into RHUA and the entitlements will be read correctly.
Copy to Clipboard Copied! - BZ#988540
This update fixes an issue with extra information being returned in a mongo query. This meant that for a setup with a large number of orphaned packages the query would throw an exception. The information returned has been reduced so that only the needed information is present and the query will be able to handle a much larger number of orphaned packages on a system.
This update fixes an issue with extra information being returned in a mongo query. This meant that for a setup with a large number of orphaned packages the query would throw an exception. The information returned has been reduced so that only the needed information is present and the query will be able to handle a much larger number of orphaned packages on a system.
Copy to Clipboard Copied! - BZ#1024812
This update fixes the synchronization status of a Content Delivery Server that has been deleted and re-added. When a Content Delivery Server was deleted and re-added the synchronization status displayed the details of the last synchronization prior to deletion. Logic has been added to determine if this is the first synchronization after the Content Delivery Server since deletion. The synchronization status now displays 'Never' if the Content Delivery Server has not been synchronized since it was re-added.
This update fixes the synchronization status of a Content Delivery Server that has been deleted and re-added. When a Content Delivery Server was deleted and re-added the synchronization status displayed the details of the last synchronization prior to deletion. Logic has been added to determine if this is the first synchronization after the Content Delivery Server since deletion. The synchronization status now displays 'Never' if the Content Delivery Server has not been synchronized since it was re-added.
Copy to Clipboard Copied!
Tools
- BZ#913097
This update fixes a problem where the status of a repository that had been deleted and re-added would show the status from a prior synchronization. This status could be confusing as a customer would expect the status to show that the re-added repository had never been synchronized. The logic had been update to understand that the prior synchronization results should be associated with the re-added repository. This makes the repository's synchronization status easier to understand.
This update fixes a problem where the status of a repository that had been deleted and re-added would show the status from a prior synchronization. This status could be confusing as a customer would expect the status to show that the re-added repository had never been synchronized. The logic had been update to understand that the prior synchronization results should be associated with the re-added repository. This makes the repository's synchronization status easier to understand.
Copy to Clipboard Copied! - BZ#1024452
This update fixes the synchronization status for a repository that has an error during synchronization. Previously the status was displayed as 'Never' until the first time the repository was successfully synchronize. The status now displays the error that has occurred.
This update fixes the synchronization status for a repository that has an error during synchronization. Previously the status was displayed as 'Never' until the first time the repository was successfully synchronize. The status now displays the error that has occurred.
Copy to Clipboard Copied! - BZ#968816
This update adds a script to the RHUA to make generation of self signed certificates easier. The cert is located at /usr/share/rh-rhua/rhui_certs/create_rhui_ssl_certs.sh. This script automates the generation of self signed certificates to make the process easier and to help prevent errors. The script creates SSL certificates for RHUA and Content Delivery Servers, as well as, a valid answers file referencing the generated certificates. This is used by a customer during initial setup of RHUI.
This update adds a script to the RHUA to make generation of self signed certificates easier. The cert is located at /usr/share/rh-rhua/rhui_certs/create_rhui_ssl_certs.sh. This script automates the generation of self signed certificates to make the process easier and to help prevent errors. The script creates SSL certificates for RHUA and Content Delivery Servers, as well as, a valid answers file referencing the generated certificates. This is used by a customer during initial setup of RHUI.
Copy to Clipboard Copied! - BZ#962408
This update adds a step for generating metadata that was not part of the upload API call. This meant that packages would be associated to a repository but the yum metadata was not updated to reflect the new packages. This caused a yum client to be unable to use these new packages. This was corrected by including the metadata generation in the upload API. The packages are now able to used by a yum client after they are uploaded.
This update adds a step for generating metadata that was not part of the upload API call. This meant that packages would be associated to a repository but the yum metadata was not updated to reflect the new packages. This caused a yum client to be unable to use these new packages. This was corrected by including the metadata generation in the upload API. The packages are now able to used by a yum client after they are uploaded.
Copy to Clipboard Copied!
Appendix A. Revision History
Revision History | |||
---|---|---|---|
Revision 1-10 | Wed Mar 25 2015 | ||
| |||
Revision 1-9 | Mon Dec 16 2013 | ||
| |||
Revision 1-8 | Mon Dec 16 2013 | ||
| |||
Revision 1-7 | Wed Feb 20 2013 | ||
| |||
Revision 1-4 | Tue Aug 28 2012 | ||
| |||
Revision 1-3 | Tue Aug 28 2012 | ||
| |||
Revision 1-2 | Tue Aug 28 2012 | ||
| |||
Revision 1-1 | Mon Aug 20 2012 | ||
|
Legal Notice
Copyright © 2013 Red Hat.
This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.