Bug 1175820

Summary: [RFE] Pulp clients should not log to files
Product: [Retired] Pulp Reporter: Randy Barlow <rbarlow>
Component: user-experienceAssignee: Sayli Karmarkar <skarmark>
Status: CLOSED UPSTREAM QA Contact: pulp-qe-list
Severity: medium Docs Contact:
Priority: medium    
Version: 2.4.0CC: cperry, mhrivnak, skarmark
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-19 01:21:21 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:

Description Randy Barlow 2014-12-18 16:29:06 UTC 
Description of problem:
pulp-admin and pulp-consumer log to files by default. This can cause concurrency issues if users run more than one command at a time. It's also inconvenient when there is an error, as the CLI tells the user "there was a problem, see the log" instead of just showing the user the error.

Most CLI programs offer -v and -vv flags. I propose that we do the same. The -v flag would cause all things that go to admin.log to go to the console. The -vv flag would do the same and also add in the server_calls.log. If the user wants these to go to files, they can use standard Unix shell redirection to accomplish that.

One exception is Exceptions ☺ We should print unexpected exceptions to the screen even in normal mode.

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

How reproducible:
Every time.

Steps to Reproduce:
1. Do pulp-admin and pulp-consumer log to files?
2. Can you adjust the console verbosity?

Actual results:
No and no.

Expected results:
Yes and yes.
Comment 1 Brian Bouterse 2015-02-19 01:21:21 UTC 
Moved to https://pulp.plan.io/issues/286