Bug 1699217

Summary: 'sendto logger #1 failed: No such file or directory (errno=2)' is shown since neutron runs neutron-haproxy-qrouter without /dev/log mount
Product: Red Hat OpenStack Reporter: Keigo Noha <knoha>
Component: openstack-tripleo-heat-templatesAssignee: Brent Eagles <beagles>
Status: CLOSED DUPLICATE QA Contact: Sasha Smolyak <ssmolyak>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 13.0 (Queens)CC: beagles, bperkins, mburns
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-19 17:02:28 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:

Description Keigo Noha 2019-04-12 07:18:48 UTC 
Description of problem:
'sendto logger #1 failed: No such file or directory (errno=2)' is shown since neutron runs neutron-haproxy-qrouter without /dev/log mount.
The message is shown at every spawn of neutron-haproxy-qrouter container.

Version-Release number of selected component (if applicable):

How reproducible:
Everytime at spawn of the neutron-haproxy-qrouter container.

Steps to Reproduce:
1. Deploy overcloud.
2. Create a private and public network. And create a router for those networks.
3. Check the message in /var/log/mesasges on the controller node which runs neutron-haproxy-qrouter container.

Actual results:
'sendto logger #1 failed: No such file or directory (errno=2)' is shown.

Expected results:
The error messages will not be shown.

Additional info:
Comment 1 Keigo Noha 2019-05-08 09:00:58 UTC 
Hi Brent-san,

The issue seems to be fixed in upstream.
The gerrit for this issue is https://review.opendev.org/#/c/648128/.

Could you consider to backport it into RHOSP13?

Best Regards,
Keigo Noha
Comment 2 Keigo Noha 2019-05-09 03:14:06 UTC 
Hi Brent-san,

This issue might be the duplicate of BZ#1651953.
If you confirm the duplication of the bugzilla, please close this bugzilla as dup of BZ#1651953.

Best Regards,
Keigo Noha