Bug 1035762 - cinder-manage host list output show debug line
Summary: cinder-manage host list output show debug line
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: 4.0
Hardware: All
OS: Linux
low
low
Target Milestone: ---
: 5.0 (RHEL 7)
Assignee: Eric Harney
QA Contact: Dafna Ron
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-28 12:13 UTC by Yogev Rabl
Modified: 2016-04-26 14:54 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-13 17:03:51 UTC
Target Upstream Version:

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


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1255951 0 None None None Never

Description Yogev Rabl 2013-11-28 12:13:42 UTC 
Description of problem:
Following the instructions of the volume migration manual, http://docs.openstack.org/admin-guide-cloud/content//volume-migration.html
When the debug flag is true in the cinder.conf file or I'm running the command: 
cinder-manage --debug host list the output will show:

cinder-manage --debug host list
host                            zone
2013-11-28 13:58:50.269 27677 DEBUG cinder.openstack.common.lockutils [req-6bc92ab2-447a-44f8-a6e2-d1c221d31e4f None None] Got semaphore "dbapi_backend" for method "__get_backend"... inner /usr/lib/python2.6/site-packages/cinder/openstack/common/lockutils.py:191
yrabl-glance01.qe.lab.tlv.redhat.com    nova
yrabl-glance01.qe.lab.tlv.redhat.com@lvm1       nova
yrabl-glance01.qe.lab.tlv.redhat.com@nfs1       nova
yrabl-glance01.qe.lab.tlv.redhat.com@gluster1   nova
yrabl-glance01.qe.lab.tlv.redhat.com@lvm2       nova


Version-Release number of selected component (if applicable):
openstack-cinder-2013.2-2.el6ost.noarch
python-cinderclient-1.0.6-2.el6ost.noarch
python-cinder-2013.2-2.el6ost.noarch

Red Hat Enterprise Linux Server release 6.5


How reproducible:
everytime 

Steps to Reproduce:
1. turn the debug flag to true or run the command with the --debug flag
2.
3.

Actual results:
the debug line appears 

Expected results:
no debug line.

Additional info:
Comment 2 Eric Harney 2013-12-02 15:28:53 UTC 
This is currently the expected behavior, from "man cinder-manage" : "The cinder-manage.log file logs output from cinder-manage."

The question then is whether --debug should print to the console or only to the log file.  cinder-manage use is a little different from cinderclient commands, so I'm not sure that this is unreasonable behavior.
Comment 3 Yogev Rabl 2013-12-03 07:40:54 UTC 
(In reply to Eric Harney from comment #2)
> This is currently the expected behavior, from "man cinder-manage" : "The
> cinder-manage.log file logs output from cinder-manage."
> 
> The question then is whether --debug should print to the console or only to
> the log file.  cinder-manage use is a little different from cinderclient
> commands, so I'm not sure that this is unreasonable behavior.

To answer the question, the --debug shouldn't print to the console but to the log in this case. the output is not informative and doesn't contribute.
Comment 4 Eric Harney 2013-12-03 13:33:27 UTC 
(In reply to Yogev Rabl from comment #3)
> the output is not informative and doesn't contribute.

Which is why it only appears if you add --debug...
Comment 5 Eric Harney 2014-01-13 17:03:51 UTC 
Bug was marked Invalid upstream and this is low sev/prio -- if we want to pursue this, it should happen there.
Note You need to log in before you can comment on or make changes to this bug.