Description of problem: Option Code of IN generated by regnum-service do not match decode via instnum.py Error may be in either installer python code or web java code, or in invalid options spreadsheet. location of error currently undefined. Steps to Reproduce: 1.hock an installation number for MCT0982 2.decode installation number using instnum.py Actual results: [jcanton@jcanton-workstation site-packages]$ ./instnum.py f9ec20b7f873da20 Product: RHEL Server Type: Entitlement Options: Premium FullProd Virt Allowed CPU Sockets: Unlimited Allowed Virtual Instances: Unlimited Package Repositories: Server VT key: 16378912 'f9ec20' checksum: 183 'b7' options: 784 'Premium FullProd Virt' socklimit: -1 'Unlimited' virtlimit: -1 'Unlimited' type: 1 'Entitlement' product: 0 'server' {'Virt': 'VT', 'Base': 'Server'} f9ec-20b7-f873-da20 [jcanton@jcanton-workstation site-packages]$ Expected results: Options: Standard FullProd Virt, rather than Premium FullProd Virt Additional info: ref also bugzilla 219519
Created attachment 149512 [details] spreadsheet used by Matt Webbink to determin proper Product Option Code key
see bug 219519 re possible mismatch between spreadsheet and python code. Am making this bug public to ensure access for engineering.
I veified with the poc code and the result is: >>> RHEL_InstNumDecoder.InstNumDecoder("f9ec20b7f873da20").getValuesExplicit() ('rhel_server', -1, -1, 103L, ['Premium', 'Virt', 'FullProd'], 1L, 1) So this seems to be an encoder problem.
Last I heard, Matt Webbink just received a new spreadsheet of sku/product option code mappings, and they are different. He needs to reconfigure all of the skus, and then we can retest. Moving to Assigned, pending this data update.
The problem was a miscommunication on my side. I had not CCed Matt on the update in December. Matt now has the current information. Bug #231377 has the data.
Sorry that was bug #219519
No code changes required. Hence no revision numbers. New spreadsheet data must be either entered or inserted into the db's. Check w/ Matt re status. Marking this bug as modified, although db update may not be yet complete.
Updated to ON_QA buy bugzillaupdater
Checkd on QA, checks good.
Fixes released