Bug 1175820 - [RFE] Pulp clients should not log to files
Summary: [RFE] Pulp clients should not log to files
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Pulp
Classification: Retired
Component: user-experience
Version: 2.4.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Sayli Karmarkar
QA Contact: pulp-qe-list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-18 16:29 UTC by Randy Barlow
Modified: 2015-03-23 01:12 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-19 01:21:21 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Pulp Redmine 286 0 None None None Never

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


Note You need to log in before you can comment on or make changes to this bug.