Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1651953

Summary: [RHOSP 13][neutron][dnsmasq] Containerized neutron's DHCP server doesn't write any logs
Product: Red Hat OpenStack Reporter: Alex Stupnikov <astupnik>
Component: puppet-tripleoAssignee: Bogdan Dobrelya <bdobreli>
Status: CLOSED ERRATA QA Contact: Roee Agiman <ragiman>
Severity: high Docs Contact:
Priority: high    
Version: 13.0 (Queens)CC: akaris, amuller, bcafarel, bdobreli, beagles, bhaley, chrisw, emacchi, fbaudin, jfindysz, jjoyce, jschluet, kmehta, kurathod, ojanas, ragiman, ralonsoh, slinaber, tvignaud
Target Milestone: ---Keywords: Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: puppet-tripleo-8.3.6-18.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1714092 (view as bug list) Environment:
Last Closed: 2019-04-30 17:27:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1714092    

Description Alex Stupnikov 2018-11-21 09:51:13 UTC 
Description of problem:

Neutron uses dnsmasq to implement DHCP/DNS servers for tenant networks. Previously we were able to troubleshoot dnsmasq issues by analysing /var/log/messages on controller nodes that are hosting active DHCP/DNS servers. A lot of information was available there: it was possible to debug every DHCP transaction there.

In RHOSP 13 dnsmasq was containerized and now it doesn't log to /var/log files or systemd units any more. Its logs are also not available inside proper container and systemd journal.

As a result, it now impossible to troubleshoot dnsmasq issues and glitches. I would like to use this bug to ask to fix described behaviour and configure proper logging for dnsmasq instances.
Comment 20 errata-xmlrpc 2019-04-30 17:27:35 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:0939