not enough logging

Bug #1290759 reported by Robert Collins
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Gregory Haynes

Bug Description

Our CI is very hard to debug - not enough logging data; HPCloud reports they run with more logging, so we probably want to say 'the default is broken' and fix locally while discussing in the -dev forum.

Revision history for this message
Robert Collins (lifeless) wrote :

http://lists.openstack.org/pipermail/openstack-operators/2014-March/004154.html seeking more information. For now I'm going to propose a change to make verbose the default in TripleO.

Revision history for this message
Haneef Ali (haneef) wrote :

We are planning to use logging.conf to customize logging. This option is there in keystone, but default setup doesn't use that. We plan to configure this for overcloud and undercloud . Is this acceptable or do we have any other solution?

https://review.openstack.org/#/c/84847/

Revision history for this message
Steven Hardy (shardy) wrote :

AFAICS, none of the services log anything at all by default in the seed/undercloud:

# ps ax | grep heat
 3687 ? Ss 0:01 /opt/stack/venvs/openstack/bin/python /opt/stack/venvs/openstack/bin/heat-api
 3699 ? Ss 0:01 /opt/stack/venvs/openstack/bin/python /opt/stack/venvs/openstack/bin/heat-api-cfn
 3709 ? Ss 0:01 /opt/stack/venvs/openstack/bin/python /opt/stack/venvs/openstack/bin/heat-api-cloudwatch
 3745 ? Ss 0:01 /opt/stack/venvs/openstack/bin/python /opt/stack/venvs/openstack/bin/heat-engine

# grep log_ /etc/heat/heat.conf
#default_log_levels=amqplib=WARN,sqlalchemy=WARN,boto=WARN,suds=INFO,keystone=INFO,eventlet.wsgi.server=WARN
#log_config=<None>
#log_format=<None>
#log_date_format=%Y-%m-%d %H:%M:%S
#log_file=<None>
#log_dir=<None>
#syslog_log_facility=LOG_USER

Because we don't set log_file, everything gets logged only to the console, which presumably means we don't log anything anywhere?

Revision history for this message
Steven Hardy (shardy) wrote :

Pls ignore that last comment - I'd missed that the console output ends up in /var/log/messages, despite use_syslog being false in the service configuration files.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-image-elements (master)

Fix proposed to branch: master
Review: https://review.openstack.org/142529

Changed in tripleo:
assignee: nobody → Gregory Haynes (greghaynes)
status: Triaged → In Progress
Revision history for this message
Brent Eagles (beagles) wrote :

The associated patch is a year old with no updates. Marking as incomplete.

Changed in tripleo:
status: In Progress → Incomplete
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on tripleo-image-elements (master)

Change abandoned by greghaynes (<email address hidden>) on branch: master
Review: https://review.openstack.org/142529
Reason: This is over a year stale

Revision history for this message
Ben Nemec (bnemec) wrote :

I'm going to call this fixed from a tripleo perspective. Logging is an ongoing discussion in OpenStack, but to my knowledge there aren't any TripleO-specific issues with it at the moment.

Changed in tripleo:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.