Bug 918617

Summary: Subscription Manager GUI does not log anything in /var/log/rhsm/rhsm.log on 'subscribe' and 'unsubscribe'
Product: Red Hat Enterprise Linux 7 Reporter: Sharath Dwaral <fsharath>
Component: subscription-managerAssignee: candlepin-bugs
Status: CLOSED NOTABUG QA Contact: IDM QE LIST <seceng-idm-qe-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: jgalipea
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-07 00:15:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 863175    

Description Sharath Dwaral 2013-03-06 15:31:03 UTC 
Description of problem:
Subscription Manager GUI does not log anything in /var/log/rhsm/rhsm.log on 'subscribe' and 'unsubscribe' where as the 'subscribe'/'unsubscribe' on CLI logs information.

Version-Release number of selected component (if applicable):

rpm -qa | egrep  'subscription-manager|python-rhsm'
subscription-manager-debuginfo-1.1.23-1.el6.x86_64
subscription-manager-migration-data-1.12.2.6-1.git.0.171d4c3.el6.noarch
python-rhsm-1.8.5-1.git.0.c3e0d11.el6.x86_64
subscription-manager-firstboot-1.8.3-1.git.14.a306b0c.el6.x86_64
subscription-manager-gui-1.8.3-1.git.14.a306b0c.el6.x86_64
subscription-manager-1.8.3-1.git.14.a306b0c.el6.x86_64
python-rhsm-debuginfo-1.1.8-1.el6.x86_64
subscription-manager-migration-1.8.3-1.git.14.a306b0c.el6.x86_64


How reproducible:
Always

Steps to Reproduce:

1. # subscription-manager-gui
   Click on  System -> register
   Register with valid credentials
   Attach Subscriptions
  
2. check log  #cat /var/log/rhsm/rhsm.log

3. Remove attached Subscriptions

4. check log  #cat /var/log/rhsm/rhsm.log
  
Actual results:
Nothing is updated in rhsm.log

Expected results:
Log file should be updated with appropriate data

Additional info:
Similar to Bug 918303
Comment 2 Sharath Dwaral 2013-03-07 00:15:29 UTC 
This was not a bug. It was a mistake from my end