Created attachment 600056 [details] wrkflow Description of problem: I believe the root cause of this issue is that this particular RHUI has both expired and valid entitlements. For what ever reason the cert_manager.valid_entitlements() call is not picking up the valid entitlements.. See the attached wrkflow..
problem is discovered on screens/client.py line 61... not sure what the root cause is yet
Created attachment 601301 [details] entitlement_recreate.txt not able to recreate atm.
moving to on_qa to see if qa can repro. If an expired cert is required please contact me.
Created attachment 603312 [details] Reproducer screen log 1 Reproducing screen log. The workflow here was: 1. with valid RHN entitlement, add few RHEL repos 2. associate some with clusters 3. remove the RHN entitlements from /etc/pki/rhui/redhat 4. upload an expired RHN entitlement 6. unassociate a repo from a cluster at will 7. creating client entitlement for any cluster fails with: no associate repos or entitlement expired 8. upload valid RHN certificate 9. retry generating client certificates 10. discrepancy between associated repos and repos available for client entitlement creation emerges Will try again on a different deployment to confirm
(In reply to comment #4) > Created attachment 603312 [details] > Reproducer screen log 1 > > Reproducing screen log. The workflow here was: > > 1. with valid RHN entitlement, add few RHEL repos > 2. associate some with clusters > 3. remove the RHN entitlements from /etc/pki/rhui/redhat > 4. upload an expired RHN entitlement > 6. unassociate a repo from a cluster at will > 7. creating client entitlement for any cluster fails with: no associate > repos or entitlement expired > 8. upload valid RHN certificate > 9. retry generating client certificates > 10. discrepancy between associated repos and repos available for client > entitlement creation emerges > > Will try again on a different deployment to confirm Build: RHEL-6.3-RHUI-2.1-20120801.0-Server-x86_64-DVD1.iso
Created attachment 603449 [details] Reproducer screen log 2 There is even a discrepancy adding all entitled repositories; besides the fact that they are assigned at will to all the clusters (the first cluster gets all the repos, the other just some custom subset), creating client entitlement shows a discrepancy from what is assigned to the cluster-1 and what is available for the client to entitle. However, I wasn't able to reproduce the comment 4 steps here. I'll retry once more with fewer repos added.
Created attachment 603461 [details] Client entitlement repos discrepancy I've just observed an issue similar to comment 6 on yet another 2.1 deployment; even though the RHN entitlement certificates were not tampered with. See the screen log attached. Build: RHEL-6.3-RHUI-2.1-20120801.0-Server-x86_64-DVD1.iso Could these be related to Bug 840005 ?
(In reply to comment #7) > Created attachment 603461 [details] > Client entitlement repos discrepancy > > I've just observed an issue similar to comment 6 on yet another 2.1 > deployment; even though the RHN entitlement certificates were not tampered > with. See the screen log attached. Build: > RHEL-6.3-RHUI-2.1-20120801.0-Server-x86_64-DVD1.iso > > Could these be related to Bug 840005 ? Its not clear to me that anything bad happened in this log
Created attachment 603579 [details] Screen log retrying steps from comment 6 This shows adding all RHN entitled repos at once causes issues both with spontaneous assignment of repos to all the clusters as well as the client entitlement discrepancy in available repos (esp. with cluster-1)...
Created attachment 603592 [details] exact milan recreate The fix for Bug 840005 was not in your build.. that is why you are hitting that issue.. See my recreate.. The issue in 840005 is unrelated to this bug
i do see one issue with this, looks like we're not filtering the list of unprotected repositories we let you choose during client config rpm creation to only those repos associated with the cluster you're working with.
fixed the issue from comment 11 in commit b087c1fa5cb7486d1060c815ad1614f62f7d0bef
Created attachment 604296 [details] Reproducer screen log -- comment 11 Reproduced comment 11 issue in RHEL-6.3-RHUI-2.1-20120810.1-Server-x86_64-DVD1.iso
This should be fixed in rh-rhui-tools-2.1.9, please use this iso to test: http://download.devel.redhat.com/devel/candidates/RHEL-6.3-RHUI-2.1-20120813.1/2.1/Server/x86_64/iso/
Created attachment 604369 [details] Verifying screen log And indeed has it been fixed in rh-rhui-tools-2.1.9, build RHEL-6.3-RHUI-2.1-20120813.1-Server-x86_64-DVD1.iso. See the screen log attached.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: For creating client configuration RPMs, the list of unprotected repositories were not filtered, so when there are both valid and expired entitlements, client entitlement certificate generation will fail with "associated repo's not found " error. ISO 2.1 has been updated so the error no longer appears.
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. http://rhn.redhat.com/errata/RHEA-2012-1205.html