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.

Description of problem:
the netconsole service is not started automatically after configure it in TUI, or after a reboot, user need to start it manually by drop to shell.

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

How reproducible:
100%

Steps to Reproduce:
1. configure netconsole in TUI.
2. drop to shell, check the netconsole service, it's not started.
3. reboot the system, check the netconsole service after reboot, it's not started.
  
Actual results:
the netconsole service is not started automatically after configure it in TUI, or after a reboot

Expected results:
start netconsole service immediately after configure it in TUI or reboot.

Test version:
rhev-hypervisor6-6.3-20120215.0.el6

Test step:
1. Configure netconsole in TUI.
2. Press F2 drop to shell, check the netconsole service, it is started.
3. Reboot the system, check the netconsole service after reboot, it's not
started.
4. Restart netconsole server can successful.

#chkconfig | grep netconsole
netconsole     	0:off	1:off	2:off	3:off	4:off	5:off	6:off

So the bug is fixed, change bug status to VERIFIED.

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Previously, once configured, the netconsole service had to be started manually. The netconsole service is now started immediately upon configuration. It is also started automatically when the Hypervisor boots, if configured.

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/RHBA-2012-0741.html