Some openstack logs is empty on UI

Bug #1320910 reported by Anastasia Palkina
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
High
Fuel Python (Deprecated)
5.0.x
Won't Fix
High
Fuel Python (Deprecated)

Bug Description

"build_id": "2014-05-19_01-10-31",
"mirantis": "yes",
"build_number": "212",
"ostf_sha": "353f918197ec53a00127fd28b9151f248a2a2d30",
"nailgun_sha": "ab7f7dfddadfe0e08a39693c6d33aa0250f20142",
"production": "docker",
"api": "1.0",
"fuelmain_sha": "9de65bfdb7e8bc7c0ec6d47dfabf4a65f8a9335b",
"astute_sha": "a3432e6e31ffd6f1c56386b2eb54afeacb74750b",
"release": "5.0",
"fuellib_sha": "b4671dcaa93d45ac219991ed3f89b512342c4777"

1. Create new environment (Ubuntu, HA)
2. Choose GRE segmentation
3. Choose Ceph for images
4. Add 3 controllers, compute, cinder, 2 ceph nodes
5. Start deployment. It was successful
6. heat-engine logs for controllers is empty on UI (see screen)
7. But heat-engine logs in /var/log/remote/node-* is not empty

Response in firebug:
{"has_more": false, "to": 1639, "entries": []}

Also in other deployment ceilometer-agent-central.log and ceilometer-alarm-evaluator.log is empty on UI.

Revision history for this message
Anastasia Palkina (apalkina) wrote :
Revision history for this message
Anastasia Palkina (apalkina) wrote :
description: updated
Changed in fuel:
assignee: nobody → Fuel Python Team (fuel-python)
Changed in fuel:
importance: Undecided → High
Revision history for this message
Anastasia Palkina (apalkina) wrote : Re: openstack logs is empty on UI
summary: - heat-engine logs is empty on UI
+ openstack logs is empty on UI
description: updated
summary: - openstack logs is empty on UI
+ Some openstack logs is empty on UI
Changed in fuel:
status: New → Confirmed
Revision history for this message
Ihor Kalnytskyi (ikalnytskyi) wrote :

The issue is in our regexp matching. The Nailgun tries to parse OpenStack logs with next regexp

    https://github.com/stackforge/fuel-web/blob/master/nailgun/nailgun/settings.yaml#L82

while some openstack services has another format. For example, heat-engine:

    2014-05-20T13:25:30.718723+00:00 info: INFO: OpenStack Heat Engine started

Since each OpenStack service might have own logging settings, I don't know how to fix in better way.

I see the following ways:

1/ Add new regexp to settings.yaml for the services with a new logging format. Bad solution, IMO.

2/ Change puppet manifests to configure all OpenStack services to log with a certain log format, so we can parse it with one regex.

3/ any suggestions?

Changed in fuel:
status: Confirmed → Triaged
Revision history for this message
Mike Scherbakov (mihgen) wrote :

I don't think it is High priority issue for 5.1. We can survive without logs in 5.0, especially if I don't see an easy solution for this bug in 5.0.

Changed in fuel:
milestone: 5.0 → 5.1
Revision history for this message
Aleksandr Didenko (adidenko) wrote :

In 5.1 (master) this is not a problem already. We've merged some logging improvements and I see no problems with logging in Fuel UI.

Dmitry Pyzhov (dpyzhov)
no longer affects: fuel/5.1.x
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.