RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 621130 - Trace back recorded in rhsm log if try to register with invalid cert or without cert
Summary: Trace back recorded in rhsm log if try to register with invalid cert or witho...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: subscription-manager
Version: 6.1
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Bryan Kearney
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks: 568421
TreeView+ depends on / blocked
 
Reported: 2010-08-04 10:52 UTC by spandey
Modified: 2015-04-23 23:56 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-19 13:41:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2011:0611 0 normal SHIPPED_LIVE new package: subscription-manager 2011-05-18 17:56:21 UTC

Description spandey 2010-08-04 10:52:57 UTC 
Description of problem:


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


How reproducible:
100%

Prerequisites
Candlepin : candlepin1.devlab.phx1.redhat.com
Client : Rhel6 client with sm version 74

Steps to repro : 
Login to client console 
install latest sm version 74 
Do not enter the path of ca.crt file in rhsm.conf.
Execute registration command using user tmgedp 

Expected Result : 
Registration process should fail and error should record in rhsm.log 

Actual Result : 
Traceback error is getting recorded in rhsm.log.

2nd scenario 
enter standalone cert path for candlepin1 in rhsm.conf file  .
execute registration command 

Result : 
Traceback error is getting recorded in rhsm.log file
Comment 2 RHEL Program Management 2010-08-04 11:27:51 UTC 
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
Comment 3 Ajay Kumar Nadathur Sreenivasan 2010-09-01 17:19:47 UTC 
spandey,
   Can you clarify whether the register command executes successfully? Traceback being recorded/not recorded in the log file is not relevant.
Comment 4 spandey 2010-09-01 19:16:14 UTC 
Hi Ajay 

Registration process is getting failed .

I mean to say rhsm.log should display proper error message 

any traceback should not recorded in rhsm.log 

Any log should be in proper format , it should not contain exception or traceback 

Please le me know if i am wrong
Comment 5 Ajay Kumar Nadathur Sreenivasan 2010-09-02 15:03:57 UTC 
Hi Sachin,
       Okay. First, let us view the sequence of steps executed along with the log file. Then we can decide whether its a bug or not. And log files are meant to have all the information messages, tracebacks etc ... so that ,when a customer faces some problems, he can send the developers the exception trace(s) which will help us(developers) fix it.
Comment 6 spandey 2010-09-02 15:37:51 UTC 
Hi Ajay 

What i mean to say is on place of trace proper error message should recorded in rhsm.log

which should contain complete info for failure 

i think we have option to convert trace or exception in to message
Comment 7 spandey 2010-09-02 17:17:41 UTC 
be getting set to the same value)
<spandey> <spandey> just i want to say trace should not display in rhsm.log
<spandey> <nadathur> why ?
<spandey> <nadathur> without the traces how can we fix bug?
<spandey> <spandey> on place of traceback we should have proper error msg
<spandey> <nadathur> that is on the console
<spandey> <nadathur> when I run some command I can show some error message to the client
<spandey> <spandey> same it should be in rhsm.log 
<spandey> <nadathur> but the traces should be logged so that future sessions can fix it
<spandey> <nadathur> okay let us take this to #candlepin and see what folks say about this
<spandey> <spandey> ok
<jsefler> dgoodwin: when creating a user with the ruby client cpc create_owner <name>    The name is the key
<dgoodwin> nadathur: spandey: seems like client should *show* error mesage, logs should contain stack trace



discuss with Ajay and Devan 

iam closing defect
Comment 9 errata-xmlrpc 2011-05-19 13:41:57 UTC 
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.

http://rhn.redhat.com/errata/RHEA-2011-0611.html
Note You need to log in before you can comment on or make changes to this bug.