Bug 1358335
Summary: | NetworkManager log messages are missing in /tmp/syslog | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Radek Vykydal <rvykydal> | ||||||
Component: | NetworkManager | Assignee: | Lubomir Rintel <lrintel> | ||||||
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 7.2 | CC: | aloughla, atragler, bgalvani, dcbw, lrintel, rkhan, thaller, vbenes | ||||||
Target Milestone: | rc | ||||||||
Target Release: | --- | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | NetworkManager-1.4.0-0.6.beta1.el7 | Doc Type: | If docs needed, set a value | ||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | |||||||||
: | 1369439 (view as bug list) | Environment: | |||||||
Last Closed: | 2016-11-03 19:27:38 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: | |||||||||
Attachments: |
|
Description
Radek Vykydal
2016-07-20 14:31:49 UTC
Dan, any hint what might be the cause? Or what we need to configure to bring it back? Our fault. Stealing this. For QA: We used to log to syslog in 7.2, but added an option to log to journal in 7.3 and unintentionally switched the default. Not a big deal in the installed system since journald listens on syslog socket there and rsyslogd sucks in the logs from journal; but makes difference in the installer environment. Any update? Requesting additional logs from reporters due to this BZ makes working on 7.3 bugs harder to Anaconda team. The 1:1.4.0-0.4.git20160727.9446481f build does not fix the problem for me. I've tested with http://download.eng.brq.redhat.com/pub/rhel/rel-eng/RHEL-7.3-20160811.0/compose/Server/x86_64/os/ having newer build NetworkManager-1.4.0-0.5.beta1.el7 but it doesn't not work with the 1:1.4.0-0.4.git20160727.9446481f either. (In reply to Radek Vykydal from comment #7) > The 1:1.4.0-0.4.git20160727.9446481f build does not fix the problem for me. > > I've tested with > http://download.eng.brq.redhat.com/pub/rhel/rel-eng/RHEL-7.3-20160811.0/ > compose/Server/x86_64/os/ having newer build > NetworkManager-1.4.0-0.5.beta1.el7 but it doesn't not work with the > 1:1.4.0-0.4.git20160727.9446481f either. oh right... there was a bug in the fix :( 1.4.0-0.6 will be it. Created attachment 1192071 [details] output of journalctl -u NetworkManager from anaconda Current nigthly http://download.eng.brq.redhat.com/pub/rhel/nightly/RHEL-7.3-20160818.n.0/compose/Server/x86_64/os/ with NetworkManager 1.4.0-0.6.beta1.el7 still does not seem to log into syslog in installer. I am attaching output of journalctl -u NetworkManager. Is there any way we can help to debug the issue? Perhaps there may be some problem also on Anaconda side? Created attachment 1192072 [details]
/tmp/syslog missing NM messages
(In reply to Radek Vykydal from comment #11) > Created attachment 1192072 [details] > /tmp/syslog missing NM messages no idea, why it still fails. It really shouldn't. Back to Lubomir :( We probably need to update our rsyslog configuration in installer. It seems that we are hitting a journald, NM, syslogd services start race condition in 7.3 in installer. Looking into it. The bug seems to be fixed on NetworkManager's side with NetworkManager-1.4.0-0.6.beta1.el7 release. Waiting for anaconda to sort out the rsyslog configuration... (In reply to Thomas Haller from comment #14) > The bug seems to be fixed on NetworkManager's side with > NetworkManager-1.4.0-0.6.beta1.el7 release. > > Waiting for anaconda to sort out the rsyslog configuration... This will be fixed in lorax: bug 1369439 NM now correctly logs into syslog. It can be read afterwards in /var/log/anaconda/syslog. 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://rhn.redhat.com/errata/RHSA-2016-2581.html |