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 1790645 - [RHEL-8.2] [kexec-tools] kdump on vlan device fails
Summary: [RHEL-8.2] [kexec-tools] kdump on vlan device fails
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: kexec-tools
Version: 8.2
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: 8.0
Assignee: Bhupesh Sharma
QA Contact: Emma Wu
URL:
Whiteboard:
Depends On: 1792001
Blocks: 1732733
TreeView+ depends on / blocked
 
Reported: 2020-01-13 20:02 UTC by Bhupesh Sharma
Modified: 2023-03-31 13:16 UTC (History)
5 users (show)

Fixed In Version: kexec-tools-2.0.20-14.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 16:43:33 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-32080 0 None None None 2023-03-31 13:16:33 UTC
Red Hat Product Errata RHBA-2020:1783 0 None None None 2020-04-28 16:43:48 UTC

Description Bhupesh Sharma 2020-01-13 20:02:46 UTC
Description of problem:
Kdump fails with network unreachable mkdumprd produces vlan config that does not get ip address for vlan on eth device. 

Version-Release number of selected component (if applicable):
kexec-tools-2.0.15-33.el7

How reproducible:
Consistently reproducible with kvm VM with eth0 and eth0.some-vlan device.  Setup kdump.conf for ssh using eth0.vlan device. kdump fails.

Steps to Reproduce:
1.  In vm with single eth0 device and eth0.160:
https://src.fedoraproject.org/rpms/kexec-tools.git
VLAN="yes"
TYPE="Vlan"
PHYSDEV="eth0"
VLAN_ID="160"
REORDER_HDR="no"
GVRP="no"
VLAN_FLAGS="NO_REORDER_HDR"
MVRP="no"
PROXY_METHOD="none"
BROWSER_ONLY="no"
BOOTPROTO="none"
IPADDR="192.168.132.2"
PREFIX="24"
GATEWAY="192.168.132.1"
DNS1="192.168.132.1"
DEFROUTE="yes"
IPV4_FAILURE_FATAL="no"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_FAILURE_FATAL="no"
IPV6_ADDR_GEN_MODE="stable-privacy"
NAME="eth0.160"
DEVICE="eth0.160"
ONBOOT="yes"

2.  Configure kdump over the eth0.160 device:
ssh kdump.132.1
sshkey /root/.ssh/id_rsa
path /var/crash/
core_collector makedumpfile -F -d 17 -c
default shell

3. Build initrd:
systemctl start kdump

Actual results:
kdump test fails.
kdump shell shows:
# ip addr show eth1
2: kdump-eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 52:54:00:27:c4:a5 brd ff:ff:ff:ff:ff:ff
3: eth0.160@kdump-eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 52:54:00:27:c4:a5 brd ff:ff:ff:ff:ff:ff


Expected results:
kdump test succeeds.
kdump eth0.160 should get ip address something like:
2: kdump-eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 52:54:00:27:c4:a5 brd ff:ff:ff:ff:ff:ff
3: eth0.160@kdump-eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 52:54:00:27:c4:a5 brd ff:ff:ff:ff:ff:ff
    inet 192.168.132.2/24 brd 192.168.132.255 scope global eth1.160
       valid_lft forever preferred_lft forever

Additional info:
Dissection of kdump initrd reveals /etc/cmdline.d/ contains these two files and contents:

40ip.conf 
  ip=192.168.132.2::192.168.132.1:255.255.255.0::kdump-eth0.160:none
43vlan.conf: 
  vlan=eth0.160:kdump-eth0 ifname=kdump-eth0:52:54:00:27:c4:a5

Which can be confirmed, in kdump shell, to build kdump-eth0 device, and eth0.160 device.  eth0.160 does not get an ip address, because the ip address expects device kdump-eth0.160.

The following solution has been tested by the customer and does allow this configuration to work on eth0.160:

diff -up /usr/lib/dracut/modules.d/99kdumpbase/module-setup.sh.orig.2 /usr/lib/dracut/modules.d/99kdumpbase/module-setup.sh
--- /usr/lib/dracut/modules.d/99kdumpbase/module-setup.sh.orig.2	2019-08-27 15:33:28.397000000 -0400
+++ /usr/lib/dracut/modules.d/99kdumpbase/module-setup.sh	2019-08-27 15:34:34.571000000 -0400
@@ -252,10 +252,10 @@ kdump_setup_vlan() {
         exit 1
     elif kdump_is_bond "$_phydev"; then
         kdump_setup_bond "$_phydev"
-        echo " vlan=$_netdev:$_phydev" > ${initdir}/etc/cmdline.d/43vlan.conf
+        echo " vlan=$(kdump_setup_ifname $_netdev):$_phydev" > ${initdir}/etc/cmdline.d/43vlan.conf
     else
         _kdumpdev="$(kdump_setup_ifname $_phydev)"
-        echo " vlan=$_netdev:$_kdumpdev ifname=$_kdumpdev:$_netmac" > ${initdir}/etc/cmdline.d/43vlan.conf
+        echo " vlan=$(kdump_setup_ifname $_netdev):$_kdumpdev ifname=$_kdumpdev:$_netmac" > ${initdir}/etc/cmdline.d/43vlan.conf
     fi
 }

That patch results in kdump-eth0.160 instead of eth0.160, which allows no changes necessary to 40ip.conf.

Comment 8 errata-xmlrpc 2020-04-28 16:43:33 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://access.redhat.com/errata/RHBA-2020:1783


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