This bug has been copied from bug #575127 and has been proposed to be backported to 5.5 z-stream (EUS).
Built package rhn-client-tools-0.4.20-33.el5_5.1
Taking QA contact for the bug verification.
I've verified that regression described in bug #575127, has been fixed in rhn-client-tools-0.4.20-33.el5_5.1 But there is another issue: Xen FV Guest consumes "Flex Guest Entitlement" even when its host is registered with [Virtualization] [Virtualization Platform]. Tested on rhel5-Server x86_64 (both host and guest) With: rhn-client-tools-0.4.20-9.el5 rhn-client-tools-0.4.20-33.el5_5.1 Is this a blocker for verifying it, or should I file another bug? Additional info: bug #575127, comment 3
Please verify if that problem with flex entitlement happens with package which was in rhel5.4 (or older). If does then it is not regression and we should track it separately. If it does not fail with that old package, then it is part of this regression and I would like to solve it in this BZ.
Changing to verified: Testing procedure: A) Host rhel5-Server/x86_64 registered to webqa with [Virtualization]. 1) Guest registered to webqa with rhnreg_ks, rhn_register (both tui and gui) 2) rhn-client-tools-0.4.20-33.el5 - Guest consumes regular ent. rhn-client-tools-0.4.20-33.el5.1 - Guest consumes FGE B) webui -> (Guest) -> Overview: Old: (nothing about virtualization) New: Virtualization: Fully Virtualized C) Simple file deploy with rhn-client-tools-0.4.20-33.el5.1 Ok Note: Behaviour in A,B was compared to rhn-client-tools-0.4.20-9.el5 Verified against: (on rhel5-Server x86_64) rhn-client-tools-0.4.20-33.el5_5.1
Please note: Add comment 6 I am unable reproduce it now and behaviour seems to be correct. I've probably made mistake first time. Inherited guest entitlements for XEN FV and PV guests are counted well. Tested on same environment against webqa and prod.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2010-0328.html