Bug 1173310

Summary: pulp-manage-db does not handle missing /dev/log gracefully
Product: [Retired] Pulp Reporter: Randy Barlow <rbarlow>
Component: user-experienceAssignee: pulp-bugs
Status: CLOSED UPSTREAM QA Contact: pulp-qe-list
Severity: medium Docs Contact:
Priority: medium    
Version: 2.4.3CC: mhrivnak, tcarlin
Target Milestone: ---Keywords: EasyFix, Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-28 22:46:39 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: 1171330    

Description Randy Barlow 2014-12-11 20:44:06 UTC
Description of problem:
If pulp-manage-db is run on a machine that does not have /dev/log, the user will see error messages that they do not understand (similar to "Nonetype has no attribute critical"). It would be better if we printed an informative error to stderr and exited with a non-zero exit code.

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

How reproducible:
Every time.

Steps to Reproduce:
1. Take some action to remove /dev/log (stopping rsyslogd might do the trick)
2. Run pulp-manage-db

Actual results:
You will get difficult-to-understand error messages on the console (and obviously, no log messages).

Expected results:
You should get a meaningful error message on the console and a non-zero exit code. Obviously, still nothing should/could be logged.

Comment 1 Thom Carlin 2014-12-11 21:39:27 UTC
1173338 is related doc bz

Comment 2 Brian Bouterse 2015-02-28 22:46:39 UTC
Moved to https://pulp.plan.io/issues/639