Red Hat Bugzilla – Bug 1320025
registering guest on unregistered host consumes regular instead of flex entitlement with spacewalk-backend-2.3.3-39.el6sat
Last modified: 2016-06-15 13:29:20 EDT
Description of problem: Registering guest (running on unregistered host) consumes regular instead of flex entitlement with spacewalk-backend-2.3.3-39.el6sat. Version-Release number of selected component (if applicable): spacewalk-backend-2.3.3-39.el6sat.noarch How reproducible: always Steps to Reproduce: 0. Ensure you are on virtual system (whose host is not registered into same Satellite): # grep -e QEMU -e KVM /proc/cpuinfo model name : QEMU Virtual CPU version (cpu64-rhel6) model name : QEMU Virtual CPU version (cpu64-rhel6) 1. with spacewalk-backend-2.3.3-33.el6sat.noarch: # rhnreg_ks --force --username=<user> --password=<pass> API org.listSoftwareEntitlements(key) returns: {'unallocated_flex': 999, 'used': 0, 'name': 'Red Hat Enterprise Linux Server (v. 6)', 'allocated_flex': 1, 'used_flex': 1, 'free': 0, 'label': 'rhel-server-6', 'free_flex': 0, 'unallocated': 14000, 'allocated': 0} => GOOD, Flex entitlement is used 2. with spacewalk-backend-2.3.3-39.el6sat.noarch: # rhnreg_ks --force --username=<user> --password=<pass> API org.listSoftwareEntitlements(key) returns: {'unallocated_flex': 1000, 'used': 1, 'name': 'Red Hat Enterprise Linux Server (v. 6)', 'allocated_flex': 0, 'used_flex': 0, 'free': 0, 'label': 'rhel-server-6', 'free_flex': 0, 'unallocated': 13999, 'allocated': 1} => BAD, regular entitlement is used Actual results: On latest version of the package, guest does not consume flex entitlements Expected results: Should consume flex entitlement.
As a workaround you can always go to Overview -> Subscription Management -> Virtualization Entitlements -> Guests Consuming Regular Entitlements and switch systems to use FLEX manually.
fixed in spacewalk master (even if the problem is not there): fc626e08c34b0be7925a15c4a29236c5cfcf3181
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. https://access.redhat.com/errata/RHBA-2016:1200