Bug 558733 - mkdumprd fails when using a network bridge
Summary: mkdumprd fails when using a network bridge
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kexec-tools
Version: 5.4.z
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Cong Wang
QA Contact: Chao Ye
URL:
Whiteboard:
: 612289 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-26 09:20 UTC by Igor Zhang
Modified: 2018-11-14 19:08 UTC (History)
5 users (show)

Fixed In Version: kexec-tools-1_102pre-106_el5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-13 23:18:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
patch to make mkdumprd bridge aware (1.85 KB, patch)
2010-01-27 15:38 UTC, Neil Horman
no flags Details | Diff
Proposed patch (1.87 KB, patch)
2010-07-02 09:40 UTC, Cong Wang
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0061 0 normal SHIPPED_LIVE kexec-tools bug fix update 2011-01-12 17:22:27 UTC

Description Igor Zhang 2010-01-26 09:20:42 UTC
Description of problem:
I configured a bridge and made it work for kvm. After that, I did "service kdump restart" and it failed. Following message poped up:
[root@localhost ~]# service kdump restart
Stopping kdump:                                            [  OK  ]
No kdump initial ramdisk found.                            [WARNING]
Rebuilding /boot/initrd-2.6.18-164.11.1.el5kdump.img
ls: /sys/class/net/br0/device: No such file or directory
...
[root@localhost ~]# brctl  show
bridge name	bridge id		STP enabled	interfaces
br0		8000.0025648f9ff0	no		vnet0
							eth0
virbr0		8000.000000000000	yes
[root@localhost ~]# ls /sys/class/net/
br0  eth0  lo  sit0  virbr0  vnet0		
[root@localhost ~]# uname -a
Linux localhost.localdomain 2.6.18-164.11.1.el5 #1 SMP Wed Jan 6 13:26:04 EST 2010 x86_64 x86_64 x86_64 GNU/Linux


Version-Release number of selected component (if applicable):
2.6.18-164.11.1.el5  RHEL-5.4.z

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:
kdump failed

Expected results:
kdump can work on a bridged NIC.

Additional info:

Comment 1 Neil Horman 2010-01-26 11:39:37 UTC
Can I have access to the system you're using so that I can work on it for a bit?

Comment 2 Igor Zhang 2010-01-27 01:35:22 UTC
I conduct a similar environment in RHTS. Go for hp-dl360g5-01.rhts.eng.bos.redhat.com.

Comment 3 Neil Horman 2010-01-27 15:38:23 UTC
Created attachment 387106 [details]
patch to make mkdumprd bridge aware

please give that a try.  Make sure you both start kdump and try a panic with it.

Comment 4 Igor Zhang 2010-01-28 02:17:40 UTC
It is still not ok.
First I configured kdump and made it using ssh. But results were:
[root@hp-dl360g5-01 ~]# service kdump restart
Stopping kdump:                                            [  OK  ]
Detected change(s) the following file(s):
  
  /etc/kdump.conf
Rebuilding /boot/initrd-2.6.18-164.11.1.el5kdump.img
/etc/kdump.conf: Could not create root.65.35:/var/crash, you probably need to run "service kdump propagate"
Failed to run mkdumprd
Starting kdump:                                            [FAILED]
[root@hp-dl360g5-01 ~]# service kdump propagate
Using existing keys...
root.65.35's password: 
/root/.ssh/kdump_id_rsa.pub has been added to ~root/.ssh/authorized_keys2 on 10.66.65.35
[root@hp-dl360g5-01 ~]# service kdump restart
Stopping kdump:                                            [  OK  ]
Detected change(s) the following file(s):
  
  /etc/kdump.conf
Rebuilding /boot/initrd-2.6.18-164.11.1.el5kdump.img
/etc/kdump.conf: Could not create root.65.35:/var/crash, you probably need to run "service kdump propagate"
Failed to run mkdumprd
Starting kdump:                                            [FAILED]
[root@hp-dl360g5-01 ~]#

Second I configured kdump and made it using nfs. But results were:
...
Scanning logical volumes
  Reading all physical volumes.  This may take a while...
  Found volume group "VolGroup00" using metadata type lvm2
Activating logical volumes
  2 logical volume(s) in volume group "VolGroup00" now active
mapping br0 to
mapping br0 to
mapping eth0 to eth0
mapping eth3 to eth3
mv: unable to rename `/etc/ifcfg-br0': No such file or directory
sed: No previous regexp.
sed: No previous regexp.
sed: No previous regexp.
mv: unable to rename `/etc/ifcfg-': No such file or directory
sed: /etc/ifcfg-tmp1: No such file or directory
BusyBox v1.2.0 (2009.07.02-14:09+0000) multi-call binary

Usage: ifup <-ahinv> <ifaces...>

ifup <options> <ifaces...>

Options:
	-h	this help
	-a	de/configure all interfaces automatically
	-i FILE	use FILE for interface definitions
	-n	print out what would happen, but don't do it
			(note that this option doesn't disable mappings)
	-v	print out what would happen before doing it
	-m	don't run any mappings
	-f	force de/configuration

 failed to come up
Restarting system.

Comment 5 Neil Horman 2010-03-08 15:03:00 UTC
hey, can you please do me a quick favor?  I just noted you opened this on 5.4.z, can you test it on latest 5.5 and see if its working?  I don't think it will, but I want to be sure as I do recall making some minor xen adjustments a while back.  Thanks!

Comment 6 Igor Zhang 2010-03-10 03:04:11 UTC
With RHEL5.5-Server-20100304.nightly_nfs-x86_64:
[root@intel-s3ea2-03 ~]# service kdump restart
Stopping kdump:                                            [  OK  ]
Detected change(s) the following file(s):
  
  /etc/kdump.conf
Rebuilding /boot/initrd-2.6.18-191.el5kdump.img
cp: cannot stat `/etc/sysconfig/network-scripts/ifcfg-br0': No such file or directory
/sbin/mkdumprd: line 428: /initrd.Vg7029/etc/ifcfg-br0: No such file or directory
ls: /sys/class/net/br0/device: No such file or directory
/etc/kdump.conf: Could not create root.65.35:/var/crash, you probably need to run "service kdump propagate"
Failed to run mkdumprd
Starting kdump:                                            [FAILED]
[root@intel-s3ea2-03 ~]# brctl show
bridge name	bridge id		STP enabled	interfaces
br0		8000.000423a69474	no		eth0
virbr0		8000.000000000000	yes		
[root@intel-s3ea2-03 ~]# uname -rm
2.6.18-191.el5 x86_64

With or without your patch, it still doesn't work on RHEL5.5-Server-20100304.nightly_nfs-x86_64. Is this what you want to see? Then need I do that again on a xen kernel?

Comment 7 Cong Wang 2010-07-02 08:27:36 UTC
Bug 602325 can be viewed as a clone of this bug for RHEL6.

Comment 8 Cong Wang 2010-07-02 08:30:32 UTC
(In reply to comment #7)
> Bug 602325 can be viewed as a clone of this bug for RHEL6.    

I provided a patch for that bug:

https://bugzilla.redhat.com/show_bug.cgi?id=602325#c1

It is based on Neil's patch above, but fixes some bugs. I will make a RHEL5 version for this bug, for you to test.

Comment 9 Cong Wang 2010-07-02 09:40:32 UTC
Created attachment 428786 [details]
Proposed patch

Please test this patch.

Comment 10 Cong Wang 2010-07-08 07:40:43 UTC
*** Bug 612289 has been marked as a duplicate of this bug. ***

Comment 11 Cong Wang 2010-07-08 07:43:35 UTC
Quote from Dave Maley:

I've tested the proposed patch from bug 602325 however there are a couple
problems I encountered.

First I had to add brctl as an extra_bin otherwise creation of br0 during kdump
failed.

After adding that I'm seeing udhcpc failures, likely the same as noted in
https://bugzilla.redhat.com/show_bug.cgi?id=602325#c1

On the same test system I'm able to successfully dump to a network target when
no bridge device is configured.  The udhcpc failyres only occur when using a
bridged device.

Comment 13 Chao Ye 2010-09-03 01:49:40 UTC
Reporduced with kexec-tools-1.102pre-77.el5:
============================================================
[root@dell-pe830-02 ~]# ifconfig 
br0       Link encap:Ethernet  HWaddr 00:12:3F:2A:54:B4  
          inet addr:10.16.64.34  Bcast:10.16.71.255  Mask:255.255.248.0
          inet6 addr: fe80::212:3fff:fe2a:54b4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:35059 errors:0 dropped:0 overruns:0 frame:0
          TX packets:262 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1832423 (1.7 MiB)  TX bytes:27396 (26.7 KiB)

eth0      Link encap:Ethernet  HWaddr 00:12:3F:2A:54:B4  
          inet6 addr: fe80::212:3fff:fe2a:54b4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:35188 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1850 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2472822 (2.3 MiB)  TX bytes:133216 (130.0 KiB)
          Interrupt:169 Memory:dfcf0000-dfd00000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:560 (560.0 b)  TX bytes:560 (560.0 b)

[root@dell-pe830-02 ~]# rpm -q kexec-tools
kexec-tools-1.102pre-77.el5
[root@dell-pe830-02 ~]# brctl show
bridge name	bridge id		STP enabled	interfaces
br0		8000.00123f2a54b4	no		eth0
[root@dell-pe830-02 ~]# service kdump status
Kdump is not operational
[root@dell-pe830-02 ~]# service kdump restart
Stopping kdump:[  OK  ]
No kdump initial ramdisk found.[WARNING]
Rebuilding /boot/initrd-2.6.18-164.el5kdump.img
ls: /sys/class/net/br0/device: No such file or directory
FS-Cache: Loaded
Starting kdump:[  OK  ]
[root@dell-pe830-02 ~]# echo c > /proc/sysrq-trigger 
SysRq : Trigger a crashdump
Memory for crash kernel (0x0 to 0x0) notwithin permissible range
�Mounting proc filesystem
Mounting sysfs filesystem
Creating /dev
Creating initial device nodes
Loading ehci-hcd.ko module
Loading ohci-hcd.ko module
Loading uhci-hcd.ko module
Loading scsi_mod.ko module
Loading sd_mod.ko module
Loading usb-storage.ko module
Waiting 8 seconds for driver initialization.
Loading libata.ko module
Loading ata_piix.ko module
Loading jbd.ko module
Loading ext3.ko module
Loading dm-mod.ko module
Loading dm-log.ko module
Loading dm-mirror.ko module
Loading dm-zero.ko module
Loading dm-snapshot.ko module
Loading bridge.ko module
Loading sunrpc.ko module
Loading lockd.ko module
Loading fscache.ko module
Loading nfs_acl.ko module
Loading nfs.ko module
Waiting for required block device discovery
Waiting for sda...Found
Creating Block Devices
Creating block device ram0
Creating block device ram1
Creating block device ram10
Creating block device ram11
Creating block device ram12
Creating block device ram13
Creating block device ram14
Creating block device ram15
Creating block device ram2
Creating block device ram3
Creating block device ram4
Creating block device ram5
Creating block device ram6
Creating block device ram7
Creating block device ram8
Creating block device ram9
Creating block device sda
Making device-mapper control node
Scanning logical volumes
  Reading all physical volumes.  This may take a while...
  Found volume group "VolGroup00" using metadata type lvm2
Activating logical volumes
  2 logical volume(s) in volume group "VolGroup00" now active
mapping br0 to lo
lo Link Up.  Waiting 60 Seconds
Continuing
udhcpc (v1.2.0) started
udhcpc[1170]: udhcpc (v1.2.0) started
Sending discover...
udhcpc[1170]: Sending discover...
Sending discover...
udhcpc[1170]: Sending discover...
Sending discover...
udhcpc[1170]: Sending discover...
No lease, failing.
udhcpc[1170]: No lease, failing.
lo failed to come up
Restarting system.


Verified with kexec-tools-1.102pre-107.el5:
============================================================
[root@dell-pe830-02 ~]# rpm -q kexec-tools
kexec-tools-1.102pre-107.el5
[root@dell-pe830-02 ~]# brctl show
bridge name	bridge id		STP enabled	interfaces
br0		8000.00123f2a54b4	no		eth0
[root@dell-pe830-02 ~]# ifconfig 
br0       Link encap:Ethernet  HWaddr 00:12:3F:2A:54:B4  
          inet addr:10.16.64.34  Bcast:10.16.71.255  Mask:255.255.248.0
          inet6 addr: fe80::212:3fff:fe2a:54b4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2286 errors:0 dropped:0 overruns:0 frame:0
          TX packets:375 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:710126 (693.4 KiB)  TX bytes:32784 (32.0 KiB)

eth0      Link encap:Ethernet  HWaddr 00:12:3F:2A:54:B4  
          inet6 addr: fe80::212:3fff:fe2a:54b4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2424 errors:0 dropped:0 overruns:0 frame:0
          TX packets:488 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:761578 (743.7 KiB)  TX bytes:44190 (43.1 KiB)
          Interrupt:169 Memory:dfcf0000-dfd00000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:560 (560.0 b)  TX bytes:560 (560.0 b)

[root@dell-pe830-02 ~]# service kdump restart
Stopping kdump:[  OK  ]
Detected change(s) the following file(s):
  
  /etc/kdump.conf
Rebuilding /boot/initrd-2.6.18-164.el5kdump.img
FS-Cache: Loaded
Starting kdump:[  OK  ]
[root@dell-pe830-02 ~]# echo c > /proc/sysrq-trigger 
SysRq : Trigger a crashdump
Memory for crash kernel (0x0 to 0x0) notwithin permissible range
�Mounting proc filesystem
Mounting sysfs filesystem
Creating /dev
Creating initial device nodes
Loading ehci-hcd.ko module
Loading ohci-hcd.ko module
Loading uhci-hcd.ko module
Loading scsi_mod.ko module
Loading sd_mod.ko module
Loading libata.ko module
Loading ata_piix.ko module
Loading jbd.ko module
Loading ext3.ko module
Loading dm-mod.ko module
Loading dm-log.ko module
Loading dm-mirror.ko module
Loading dm-zero.ko module
Loading dm-snapshot.ko module
Loading usb-storage.ko module
Waiting 8 seconds for driver initialization.
Loading bridge.ko module
Loading tg3.ko module
Loading sunrpc.ko module
Loading lockd.ko module
Loading fscache.ko module
Loading nfs_acl.ko module
Loading nfs.ko module
Waiting for required block device discovery
Waiting for sda...Found
Creating Block Devices
Creating block device ram0
Creating block device ram1
Creating block device ram10
Creating block device ram11
Creating block device ram12
Creating block device ram13
Creating block device ram14
Creating block device ram15
Creating block device ram2
Creating block device ram3
Creating block device ram4
Creating block device ram5
Creating block device ram6
Creating block device ram7
Creating block device ram8
Creating block device ram9
Creating block device sda
Making device-mapper control node
Scanning logical volumes
  Reading all physical volumes.  This may take a while...
  Found volume group "VolGroup00" using metadata type lvm2
Activating logical volumes
  2 logical volume(s) in volume group "VolGroup00" now active
mapping br0 to br0
mapping eth0 to eth0
br0 Link Up.  Waiting 60 Seconds
Continuing
udhcpc (v1.2.0) started
udhcpc[1252]: udhcpc (v1.2.0) started
Sending discover...
udhcpc[1252]: Sending discover...
Sending discover...
udhcpc[1252]: Sending discover...
Sending discover...
udhcpc[1252]: Sending discover...
Sending select for 10.16.64.34...
udhcpc[1252]: Sending select for 10.16.64.34...
Lease of 10.16.64.34 obtained, lease time 86400
udhcpc[1252]: Lease of 10.16.64.34 obtained, lease time 86400
deleting routers
adding dns 10.16.36.29
adding dns 10.16.255.2
adding dns 10.16.255.3
Saving to remote location nest.test.redhat.com:/mnt/qa
Saving core complete
Restarting system.

============================================================
Change status to VERIFIED.

Comment 17 errata-xmlrpc 2011-01-13 23:18:07 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0061.html


Note You need to log in before you can comment on or make changes to this bug.