Bug 1274647

Summary: Set NetworkManager log level to debug in anaconda
Product: Red Hat Enterprise Linux 7 Reporter: Radek Vykydal <rvykydal>
Component: loraxAssignee: Brian Lane <bcl>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: high    
Version: 7.2CC: dcbw, mbanas, mkovarik, salmy
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: lorax-19.6.67-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-03 23:44:49 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 Flags
a patch setting NM loglevel to DEBUG in anaconda none

Description Radek Vykydal 2015-10-23 09:12:53 UTC
Setting NetworkManager log level to debug in anaconda would save us significant amount of time when debugging network related issues.

Comment 2 Radek Vykydal 2015-10-23 09:16:06 UTC
Created attachment 1085751 [details]
a patch setting NM loglevel to DEBUG in anaconda

Comment 3 Radek Vykydal 2015-10-23 09:22:45 UTC
Dan, do you think it is a good idea? Are there any caveats?

Comment 4 Dan Williams 2016-02-19 23:57:15 UTC
Radek, I think that's fine, as long as it's removed after anaconda is done.

Comment 8 errata-xmlrpc 2016-11-03 23:44:49 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://rhn.redhat.com/errata/RHBA-2016-2165.html