Bug 1376442 - [rfe] rhn-schema-version crash with db-server stopped
Summary: [rfe] rhn-schema-version crash with db-server stopped
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Monitoring
Version: 570
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Grant Gainey
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-15 12:39 UTC by Konstantin Trufanov
Modified: 2019-12-16 06:46 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-19 15:29:19 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Konstantin Trufanov 2016-09-15 12:39:58 UTC 
Description of problem: 

rhn-schema-version crashed when it can't connect to database

# /usr/bin/rhn-schema-version
Traceback (most recent call last):
  File "/usr/bin/rhn-schema-version", line 49, in <module>
    rhnSQL.initDB()
  File "/usr/lib/python2.6/site-packages/spacewalk/server/rhnSQL/__init__.py", line 151, in initDB
    closeDB()
  File "/usr/lib/python2.6/site-packages/spacewalk/server/rhnSQL/__init__.py", line 189, in closeDB
    __DB.commit()
  File "/usr/lib/python2.6/site-packages/spacewalk/server/rhnSQL/driver_postgresql.py", line 230, in commit
    self.dbh.commit()
AttributeError: Database instance has no attribute 'dbh'
#



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

5.7

How reproducible: 

Every time if db server stopped

Steps to Reproduce:
1. Stop the database
2. Run /usr/bin/rhn-schema-version 
3.

Actual results:

/usr/bin/rhn-schema-version crash


Expected results:

error message without crashing

Additional info:
Comment 1 Grant Gainey 2016-09-19 15:29:19 UTC 
Given that this exception can only happen if the database you're trying to query is inaccessible, and given that Satellite5 is in Production Phase 3 support, we have no plans to address this request.
Note You need to log in before you can comment on or make changes to this bug.