Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 765898

Summary: netconsole does not work
Product: Red Hat Enterprise Linux 6 Reporter: RHEL Program Management <pm-rhel>
Component: ovirt-nodeAssignee: Mike Burns <mburns>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: urgent    
Version: 6.2CC: acathrow, apevec, bgollahe, bsarathy, cshao, gouyang, jboggs, jpallich, kli, leiwang, mburns, moli, ovirt-maint, pm-eus, ycui
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-node-2.0.2-0.14.3.git3eac501.el6_2.1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-22 17:26:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 755458    
Bug Blocks:    

Description RHEL Program Management 2011-12-09 16:24:05 UTC
This bug has been copied from bug #755458 and has been proposed
to be backported to 6.2 z-stream (EUS).

Comment 4 Mike Burns 2011-12-09 16:34:28 UTC
Patch backported from 6.3 bug

Comment 6 Guohua Ouyang 2011-12-12 02:36:53 UTC
verified on rhevh 6.2-20111209.1 build, after configure netconsole address in logging, drop to shell start netconsole service correctly, try a simple test $("echo "test message" > /dev/kmsg), it works, can see "test message" in remote server log file..

I think there is still a minor enhancement is that start the netconsol service immediately after it's configured in TUI, then user no need to start the service manually by drop to shell.   Please consider if we need to do this.

Comment 7 Mike Burns 2011-12-12 13:07:09 UTC
Does the netconsole service start correctly after a reboot?

Please file a separate bug to track not starting netconsole service.  We should be starting the service on boot and (re)starting after configuration.

Comment 8 Guohua Ouyang 2011-12-13 03:16:29 UTC
(In reply to comment #7)
> Does the netconsole service start correctly after a reboot?
the netconsole service does not start correctly after a reboot

> Please file a separate bug to track not starting netconsole service.  We should
> be starting the service on boot and (re)starting after configuration.

a separate bug 767038  is filed for this feature.


Since the netconsole service can be started by manually, hence close this bug.

Comment 9 errata-xmlrpc 2011-12-22 17:26:22 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.

http://rhn.redhat.com/errata/RHSA-2011-1850.html