Provide a configuration driven way to disable package reporting. This should override the default behaviour of reporting if the upstream server supports accepting the data.
commit e8ba669b297ac1af71e1ffd082c31ad5667916b9 Author: Bryan Kearney <bkearney> Date: Fri Jan 25 16:56:38 2013 -0500 Give users the ability to disable package reporting This is done via a new setting in the rhsm.conf file. If the setting report_package_profile = 1 is changed to zero then the package profile will not be sent up. This setting has no impact if the backend service does not suppot package uploads.
Fixed in the 1.8.2 version of subscription-manager or python-rhsm
Created attachment 742720 [details] The before and after images are the same as i dont see any changes # rpm -qa | egrep "subscription-manager|python-rhsm" subscription-manager-migration-1.8.6-1.git.27.f8647f0.el5 subscription-manager-1.8.6-1.git.27.f8647f0.el5 subscription-manager-migration-data-1.11.2.7-1.git.0.1dfd00e.el5 subscription-manager-gui-1.8.6-1.git.27.f8647f0.el5 subscription-manager-firstboot-1.8.6-1.git.27.f8647f0.el5 python-rhsm-1.8.9-1.git.7.214419e.el5 Steps: cat /etc/rhsm/rhsm.conf | grep report_package_profile -A1 -B3 # If set to zero, the client will not report the package profile to # the subscription management service. report_package_profile = 1 # subscription-manager register --org=ACME_Corporation --environment=DEV Username: admin Password: The system has been registered with ID: 8b98640e-536a-43a0-bfd8-966f86a09d19 Packages displayed (refer attachment) Remove System from Katello Server # subscription-manager unregister Consumer 8b98640e-536a-43a0-bfd8-966f86a09d19 has been deleted # subscription-manager clean All local data removed # edit /etc/rhsm/rhsm.conf -> report_package_profile = 0 cat /etc/rhsm/rhsm.conf | grep report_package_profile -A1 -B3 # If set to zero, the client will not report the package profile to # the subscription management service. report_package_profile = 0 # service rhsmcertd restart Stopping rhsmcertd... [ OK ] Starting rhsmcertd... [ OK ] # subscription-manager register --org=ACME_Corporation --environment=DEV Username: admin Password: The system has been registered with ID: 0334f979-afe1-4923-a7da-64d6e723db41 Packages are still displayed (refer attachment) QE_FAIL Moving to bug to NEW
Need to treat the value as an int, not a string. https://github.com/candlepin/subscription-manager/pull/585
*** Bug 922839 has been marked as a duplicate of this bug. ***
commit cc0074ebb0be4c7022571632082c5c8296373b3e Author: Bryan Kearney <bkearney> Date: Tue May 7 13:02:53 2013 -0400 905922: use get_int instead of get in order to consume the value as a booolean
delivered in the latest errata.
Verifying with Versions... [root@jsefler-5 ~]# subscription-manager version server type: This system is currently not registered. subscription management server: 1.4.2-1.git.765.078bebf.el6-Katello subscription-manager: 1.8.11-1.el5 python-rhsm: 1.8.12-1.el5 VERIFYING report_package_profile = 1 [root@jsefler-5 ~]# grep report_package_profile /etc/rhsm/rhsm.conf report_package_profile = 1 [root@jsefler-5 ~]# subscription-manager register --username admin --org SimpleOrg --env DEV Password: The system has been registered with ID: cadbf1ac-8146-4d2e-8ab5-95028a5fda05 [root@jsefler-5 ~]# See attached screenshot showing system in Katello with report_package_profile = 1 VERIFYING report_package_profile = 0 [root@jsefler-5 ~]# subscription-manager unregister System has been unregistered. [root@jsefler-5 ~]# subscription-manager config --rhsm.report_package_profile=0 [root@jsefler-5 ~]# grep report_package_profile /etc/rhsm/rhsm.conf report_package_profile = 0 [root@jsefler-5 ~]# subscription-manager register --username admin --org SimpleOrg --env DEV Password: The system has been registered with ID: f14bb190-e634-41ca-897f-b66c78d1d04a [root@jsefler-5 ~]# See attached screenshot showing system in Katello with report_package_profile = 0
Created attachment 767957 [details] screenhots of Katello showing package_profile reported based on rhsm.report_package_profile set to 0 or 1
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. http://rhn.redhat.com/errata/RHBA-2013-1332.html