GlusterFS container capture the entries which should be inserted into worker node syslog, the issue only happens on the GlusterFS storage node.
Steps for reproduction:
On the worker node which also used as glusterFS storage node, run this commands to insert a record into host syslog:
logger -is -p auth.err authpriv-test
Check the worker node syslog or run "journalctl -r" command to check, nothing was inserted into worker node syslog.
Now, login the glusterfs container which running on this worker node, run "journalctl -r" command to check, found that record was inserted into the container syslog.
The implication of this behavior is that the log of "secure", "maillog", "spooler", "boot.log" will be captured by the glusterFS container syslog and missed in node syslog, this caused user can not monitor the node's syslog correctly.
GlusterFS container capture the entries which should be inserted into worker node syslog, the issue only happens on the GlusterFS storage node.
Steps for reproduction:
On the worker node which also used as glusterFS storage node, run this commands to insert a record into host syslog:
Check the worker node syslog or run "journalctl -r" command to check, nothing was inserted into worker node syslog.
Now, login the glusterfs container which running on this worker node, run "journalctl -r" command to check, found that record was inserted into the container syslog.
The implication of this behavior is that the log of "secure", "maillog", "spooler", "boot.log" will be captured by the glusterFS container syslog and missed in node syslog, this caused user can not monitor the node's syslog correctly.