Dnsqmasq logs missed

Bug #1357408 reported by Igor Shishkin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Committed
High
Matthew Mosesohn

Bug Description

http://jenkins-product.srt.mirantis.net:8080/job/fuel_master.ubuntu.bvt_2/274/console

......
[root@62d58f108849 ~]# cat /etc/dnsmasq.conf
# Cobbler generated configuration file for dnsmasq
# Fri Aug 15 14:41:04 2014

read-ethers
log-dhcp
log-queries
log-facility=LOCAL0
addn-hosts = /var/lib/cobbler/cobbler_hosts
domain=local
.....

[root@62d58f108849 ~]# egrep -i 'dnsmasq|dhcp' /var/log/syslog
[root@62d58f108849 ~]# egrep -i 'dnsmasq|dhcp' /var/log/messages
[root@62d58f108849 ~]#

Tags: cobbler puppet
Changed in fuel:
milestone: 6.0 → 5.1
Igor Shishkin (teran)
Changed in fuel:
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Igor Shishkin (teran) wrote :

I've got this on fuel-master-438-2014-08-14_19-21-57.iso

dnsmasq logs are missed on master node withing cobbler container and outside it.
It looks like messages doesn't come to syslog because dnsmasq configration looks good.

Revision history for this message
Mike Scherbakov (mihgen) wrote :

Could you please clarify the severity of this issue, i.e. how does it affect usability, UX, operations, etc. If it's just forgotten log file, I don't think it should we a High priority and be part of the counter for HCF criteria.

Revision history for this message
Vladimir Kuklin (vkuklin) wrote :

It looks like this bug severity is not high as it does not affect deployment and the functionality of cluster.

Changed in fuel:
milestone: 5.1 → 6.0
Changed in fuel:
assignee: Fuel Library Team (fuel-library) → Matthew Mosesohn (raytrac3r)
Revision history for this message
Matthew Mosesohn (raytrac3r) wrote :

I can confirm we're missing these logs because rsyslog does not run on the Cobbler container. We have two options to solve this: one is to run dnsmasq with --log-facility=/var/log/dnsmasq.log. The other is to run rsyslog daemon in a custom mode and reroute logs to the rsyslog container. It's a little tricky because there will be collision in the /var/log/messages file. I prefer we just log directly to a file and allow Cobbler to be more autonomous as it is now.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-library (master)

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

Changed in fuel:
status: Confirmed → In Progress
Changed in fuel:
milestone: 6.0 → 5.1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-library (master)

Reviewed: https://review.openstack.org/116883
Committed: https://git.openstack.org/cgit/stackforge/fuel-library/commit/?id=d36e1cf3984997d6923d923cb9eb94f6230fef21
Submitter: Jenkins
Branch: master

commit d36e1cf3984997d6923d923cb9eb94f6230fef21
Author: Matthew Mosesohn <email address hidden>
Date: Tue Aug 26 16:39:15 2014 +0400

    Direct dnsmasq logs to file for Cobbler

    Since rsyslog does not run in Cobbler
    docker container, its logs should be
    directed to a file.

    Change-Id: I9cf9dd9baca5d09e26bb315211eccf6fe74060b4
    Closes-Bug: #1357408

Changed in fuel:
status: In Progress → Fix Committed
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.