Description of problem: Satellite-5.6-Beta2 is going to be allowed to activate against Hosted. This process requires coordination between AMS, Satellite, and GCA-DB. This BZ is to track the SQL changes necessary. Please add mapping product to channel for those products. The satellite channels will be named: redhat-rhn-satellite-5.6-beta-server-s390x-6 redhat-rhn-satellite-5.6-beta-server-x86_64-6 redhat-rhn-satellite-5.6-beta-server-s390x-5 redhat-rhn-satellite-5.6-beta-server-x86_64-5 (only x86_64 and s390 are supported) Channels for Satellite/RHEL6 exist in rhn.qa.redhat.com; a ticket has been submitted to RCM to create the RHEL5 versions, as of 7-JUN-2013. You can test Satellite5.6beta activation with certificate: https://satcert.gsslab.rdu2.redhat.com/viewvc/svnrepos/trunk/pm/satellite-certs/satellite-5.6beta/rhn-entitlement-cert.xml.2?revision=212513&content-type=text/plain and using: rhn-satellite-activate --rhn-cert cert5.6 --ignore-version-mismatch Current output: [root@xn--ufuk-xpa16d5h ~]# rhn-satellite-activate --rhn-cert cert5.6 --ignore-version-mismatch RHN_PARENT: xmlrpc.rhn.qa.redhat.com Error reported from RHN: <Fault -211: 'Invalid channel'> ERROR: unhandled XMLRPC fault upon remote activation: <Fault -211: 'Invalid channel'> Expected output: flawless activation The DBCHANGE required is: To Add/Change/Commit: --------------------- 1 - Add 5.6beta product versions: INSERT INTO rhnChannelProduct (id, product, version, beta) VALUES (rhn_channelprod_id_seq.NEXTVAL, 'RHN Satellite', '5.6beta', 'N'); INSERT INTO rhnChannelProduct (id, product, version, beta) VALUES (rhn_channelprod_id_seq.NEXTVAL, 'RHN Proxy', '5.6beta', 'N'); 2 - Add Satellite 5.6beta mappings to this new product version: UPDATE rhnChannel SET channel_product_id = (SELECT id FROM rhnChannelProduct WHERE product = 'RHN Satellite' AND version = '5.6beta') WHERE label in ( 'redhat-rhn-satellite-5.6-beta-server-s390x-6', 'redhat-rhn-satellite-5.6-beta-server-x86_64-6', 'redhat-rhn-satellite-5.6-beta-server-s390x-5', 'redhat-rhn-satellite-5.6-beta-server-x86_64-5' ); To Verify: ---------- 1. SELECT * FROM rhnChannelProduct where product = 'RHN Satellite' and version = '5.6beta'; should have 1 row selected with a valid ID and BETA equal to 'N' 2. SELECT ID,LABEL,CHANNEL_PRODUCT_ID from rhnChannel WHERE label like 'redhat-rhn-satellite-5.6-beta-%-%-%'; each should have 4 rows selected with a valid ID and CHANNEL_PRODUCT_ID equal to the ID value of the first test query. Satellite-5.6-BETA2 is slated to be made available to customers on 27-JUN-2013; this change will need to make its way to PROD on or before that date. Sorry for the late notice - let me know if there are any questions! Grant (NOTE: This change was already run in RHNQA to make testing beta2-activation possible.) Additional info: Needed by 27-JUN, 2013. refer INC0059776
Spoke to Grant and made two changes to the queries. 1) We set beta flag to Y instead of N. 2) removed insert for RHN Proxy, That isn't part of the beta.
dbchange looks good!
Testing Steps Quick Reference 1) create new user 2) grant-sku.cgi: MCT0370 qty 1 3) generate sat cert in portal UI 4) ssh to am-satellite, register system to new account/env and activate the satellite (see: 'history' command) Activation should pass.
http://git.corp.redhat.com/cgit/rhn/rhn/commit/?id=f2633888d05a6d6776e4616e3d9b627eacbf388a On dev and ready to test.
We need to include the 5.6beta version in the getVersions API. I've made the code change, pending review.
Code review complete http://git.corp.redhat.com/cgit/rhn/rhn/commit/?id=8d8e504a6df7dfef185fdcdf6d983d987b567d83 Use the following command on am-rhn2.devlab.phx1.redhat.com: python /git/rhn-hosted/java/rhn/xml_rpc_api/callAnyMethod.py dev2 public.satellite.getVersions rhn-noc redhat This is ready to test.
moved to version 6.1.8: http://git.corp.redhat.com/cgit/rhn/rhn/commit/?id=a61ec390d15c61b2341eb338c7b9b6b720f0cb61
verified on ams-dev2 Link to test run - https://tcms.engineering.redhat.com/run/66827/
Do not understand why must generate certificate with account that has MCT0370 first, then upload certificate after user is granted SKU SYS1192 or SYS0962. Steps to Reproduce: 1. Create new login - ny_0624q1 2. Grant the following SKUs to user: MCT0370, SYS1192 and SYS0062 3. Register system - rhnreg_ks --serverUrl http://xmlrpc.rhn.qa.redhat.com/XMLRPC --username ny_0624q1 --password redhat --force 4. Generate satellite certificate - python callAnyMethod.py qa public.satellite.generateCertificate ITENGRHNUSER redhat 6567000 5.6beta '{@2902367 : 1}' > certificate.xml Expected result - certificate should be generated successfully Actual result - Traceback (most recent call last): File "callAnyMethod.py", line 157, in <module> main(sys.argv) File "callAnyMethod.py", line 149, in main res = obj(*rpc_args) 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 verbose=self.__verbose 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 return u.close() File "/usr/lib64/python2.6/xmlrpclib.py", line 838, in close raise Fault(**self._stack[0]) xmlrpclib.Fault: <Fault 10064: 'Tried to generate certificate for Multi Satellite Org: '> Executed above test with following logins: ny_0621q2 and ny_0621qqq. ***Workaround - Grant user MCT0370 only, then generated the certificate. After certificate is generated, grant the user the skus - SYS0962 and SYS1198. Now user can successfully upload the certificate. ----------------------------------------------------------------------- NOTE: In dev2, 5.6 beta certificate is generated and activated for account that has MCT0370, SYS1192 and SYS0062. Login=ny_0624d22
verified on qa SKU configuration. In QA should only use 1 of the SKUs - SYS0962 or SYS1198.
Pushed to production 06/27