[fluentd] request ids are not always present so are handled incorrectly when logs are passed

Bug #2044366 reported by Matt Crees
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-ansible
New
Undecided
Unassigned

Bug Description

The format1 regex for extracting info out of the logs does not match on some logs:
https://github.com/openstack/kolla-ansible/blob/d6844dc8958792d900663c1c51d18cd9d7b50390/ansible/roles/common/templates/conf/input/00-global.conf.j2#L19

This part of the regex assumes the request id will follow a string:

\[(\S+ req-)?((?<request_id>\S+)

This is not always the case. Has been seen in logs from Nova Compute.

There is no request id:

2023-11-14 20:46:33 +0000 [warn]: #0 pattern not matched: "2023-11-14 20:46:33.922 7 ERROR nova.compute.manager [instance: 341b46
c8-1584-42b7-a866-2b1fe1fde093] Traceback (most recent call last):"

2023-11-14 20:46:33 +0000 [warn]: #0 pattern not matched: "2023-11-14 20:46:33.922 7 ERROR nova.compute.manager [instance: 341b46c8-1584-42b7-a866-2b1fe1fde093] self._call_wait_func(context, wait_func, volume_api, vol['id'])"

2023-11-14 20:46:33 +0000 [warn]: #0 pattern not matched: "2023-11-14 20:46:33.922 7 ERROR nova.compute.manager [instance: 341b46c8-1584-42b7-a866-2b1fe1fde093] File \"/var/lib/kolla/venv/lib64/python3.9/site-packages/nova/virt/block_device.py\", line 790, in _call_wait_func"

This is a follow-up to this bug: https://bugs.launchpad.net/kolla-ansible/+bug/1872220

Matt Crees (mattcrees)
description: updated
summary: - [fluentd] request ids are not always handled correctly when logs are
- passed
+ [fluentd] request ids are not always present so are handled incorrectly
+ when logs are passed
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.