Red Hat Bugzilla – Bug 860117
RHUA Entitlement Gen Maps Selected Repos to Wrong Repos
Last modified: 2013-03-18 08:52:39 EDT
Description of problem:
When generating an entitlement cert comprised of multiple custom repos, the repos are selected; however, when asked for confirmation the wrongs repos are selected.
Version-Release number of selected component (if applicable):
Create two CDS clusters, create multiple custom repos, try to create an entitlement RPM. The final selected repos (those shown during confirmation) do not match those selected.
Steps to Reproduce:
1. Create two CDS clusters
2. Create multiple custom repos and associate with CDS cluster A
3. Build an entitlement cert
4. Select all the associated repos, complete information
5. At the confirmation stage, observer the selected repos. They do not match those selected previously.
Invalid content entitlement and subsequent rpm
Correct content entitlement
Created attachment 616810 [details]
First show the repos
Created attachment 616811 [details]
Next shown the repos being confirmed - the "prod" repo should not be there.
Created attachment 616812 [details]
Confirm by showing the DEV cluster detail. the "prod" custom repo is not associated with this cluster
There was a bug in the process where we figured out which repos were actually selected.
Fixed in commit b4705a9f708039bd93c4818bbb7147809c1394b7
built into rh-rhui-tools-2.1.13-1.el6_3, make sure you have this version when testing the update
make sure you've updated to rh-rhui-tools-2.1.13. Follow the RHUI update procedure as outlined in the RHUI Administration guide to get the updated package, however, sync your RHUI repos from cdn.rcm-qa.redhat.com instead of cdn.redhat.com in order to get this updated package.
Entitlement certificate creation needs to be thoroughly tested. Have at least 2 clusters with different sets of custom repos (there should be some overlap, and also some repos that are also only on each cluster).
For each cluster, verify the list of repos to choose to include in an entitlement certificate is correct during certificate generation. Choose various combinations during the certificate creation, such as:
- the first repo in the list
- the last repo in the list
- all custom repos
- no custom repos
- >1 repo in the list, but not all
Verify the entitlements for the correct repos you chose are displayed in the last question of the entitlement certificate generation where it asks you to confirm your choice.
Also verify the correct repo entitlements were included in the entitlement certificate that was actually generated. Use openssl to view the text content of the cert.
Created attachment 618204 [details]
RHUI update log
Successfully updated to rh-rhui-tools-2.1.13-1.el6_3
Created attachment 618205 [details]
Verifying screen log
The issue was solved having updated to rh-rhui-tools-2.1.13-1.el6_3
- verified in EC2 staging environment
- rh-rhui-tools-2.1.13-1.el6_3.noarch.rpm not signed
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.