Red Hat Bugzilla – Bug 640958
org.setSoftwareFlexEntitlements vs org.setSoftwareEntitlements, setting reg. ent. set flex to zero and vice-versa
Last modified: 2011-03-17 10:11:58 EDT
Description of problem:
after using rpc call org.setSoftwareFlexEntitlements, regular entitlements are zeroized and same with org.setSoftwareEntitlements.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create org in satellite
2. call org.setSoftwareEntitlements e.g. 100 entit. for 'rhel-server' channel label
3. check in webui
4. call org.setSoftwareFlexEntitlements e.g. 10 entit. 'rhel-server' channel label
5. check in webui
6. rhel-server channel has 'None Alloted'
value '0' in flex, when called org.setSoftwareEntitlements and similar behaviour with org.setSoftwareFlexEntitlements
callling org.setSoftwareFlexEntitlements sets only flex entitlement value and callling org.setSoftwareEntitlements sets only regular entitlement value for particular channel
when this is called for organization which alredy has consumed some regular entitlement, rpc call returns this traceback:
Traceback (most recent call last):
File "<stdin>", line 3, in <module>
File "/usr/lib64/python2.6/xmlrpclib.py", line 1199, in __call__
return self.__send(self.__name, args)
File "/usr/lib64/python2.6/xmlrpclib.py", line 1489, in __request
File "/usr/lib64/python2.6/xmlrpclib.py", line 1253, in request
return self._parse_response(h.getfile(), sock)
File "/usr/lib64/python2.6/xmlrpclib.py", line 1392, in _parse_response
File "/usr/lib64/python2.6/xmlrpclib.py", line 838, in close
xmlrpclib.Fault: <Fault 2800: 'redstone.xmlrpc.XmlRpcFault: Warning: Your Proposed Red Hat Enterprise Linux (core server) allocation provides less entitlements than are currently in use in the OrgB organization. Please adjust your proposed allocation to no less then the amount of entitlements currently in use.'>
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.
Wrong logic of adjusting amount of software entitlements
When setting amount of software entitlements or flex entitlements using API, the other entitlements amount was zeroed
When setting amount of software entitlements or flex entitlements using API, the other entitlements amount remains untouched
null pointer exception fixed ...
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.