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.
Description of problem:
VLAN interface fails to come up when ifdown eth1.XXX; ifup eth1.XXX command is executed.
Version-Release number of selected component (if applicable):
initscripts-9.03.53-1.el6.x86_64
How reproducible:
Always
Steps to Reproduce:
$cat ifcfg-eth1.100
DEVICE=eth1.100
TYPE=Ethernet
ONBOOT=no
NM_CONTROLLED=no
BOOTPROTO=none
IPADDR=192.168.1.100
VLAN=yes
LINKDELAY=0
#ifup eth1.100
Determining if ip address 192.168.1.100 is already in use for device eth1...
[root@localhost Desktop]#
#ifdown eth1.100; ifup eth1.100
arping: recvfrom: Network is down <<<<<
#ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
2: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 52:54:00:30:09:21 brd ff:ff:ff:ff:ff:ff
3: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 52:54:00:98:3b:1f brd ff:ff:ff:ff:ff:ff
inet 10.10.10.253/24 brd 10.10.10.255 scope global eth2
28: eth1.100@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
link/ether 52:54:00:30:09:21 brd ff:ff:ff:ff:ff:ff
$ps auxwww |grep ifup
root 3306 0.2 0.1 108748 1976 ? S< 11:50 0:00 /bin/bash /etc/sysconfig/network-scripts/ifup-eth ifcfg-eth1.100
root 3353 0.0 0.0 103320 828 pts/0 S+ 11:51 0:00 grep ifup
Actual results:
1. VLAN interface fails to come up with configured IP.
2. The ifup process keeps running. cu also observed these process in 'Z' state
Expected results:
VLAN interface up with configured IP
Additional info:
1. The issue not observed in RHEL 7.
2. Issue observed for VLAN interfaces.
3. Tried to reproduce it for alias interfaces (eth1:0). But was not success. Command executed successfully.
I was not able to reproduce the issue, could you please tell your customer to boot with "rc.debug" on kernel cmdline, reproduce the issue and post here output of "dmesg"?
Comment 4Abdelfattah CHEHAB
2016-11-14 10:36:57 UTC
(In reply to Lukáš Nykrýn from comment #1)
> I was not able to reproduce the issue, could you please tell your customer
> to boot with "rc.debug" on kernel cmdline, reproduce the issue and post here
> output of "dmesg"?
the bug is reproduced on any fresh installed RHEL6.8 and eariler please find attached logs you asked for
Comment 5Abdelfattah CHEHAB
2016-11-14 10:37:59 UTC
Description of problem: VLAN interface fails to come up when ifdown eth1.XXX; ifup eth1.XXX command is executed. Version-Release number of selected component (if applicable): initscripts-9.03.53-1.el6.x86_64 How reproducible: Always Steps to Reproduce: $cat ifcfg-eth1.100 DEVICE=eth1.100 TYPE=Ethernet ONBOOT=no NM_CONTROLLED=no BOOTPROTO=none IPADDR=192.168.1.100 VLAN=yes LINKDELAY=0 #ifup eth1.100 Determining if ip address 192.168.1.100 is already in use for device eth1... [root@localhost Desktop]# #ifdown eth1.100; ifup eth1.100 arping: recvfrom: Network is down <<<<< #ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo 2: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 52:54:00:30:09:21 brd ff:ff:ff:ff:ff:ff 3: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 52:54:00:98:3b:1f brd ff:ff:ff:ff:ff:ff inet 10.10.10.253/24 brd 10.10.10.255 scope global eth2 28: eth1.100@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP link/ether 52:54:00:30:09:21 brd ff:ff:ff:ff:ff:ff $ps auxwww |grep ifup root 3306 0.2 0.1 108748 1976 ? S< 11:50 0:00 /bin/bash /etc/sysconfig/network-scripts/ifup-eth ifcfg-eth1.100 root 3353 0.0 0.0 103320 828 pts/0 S+ 11:51 0:00 grep ifup Actual results: 1. VLAN interface fails to come up with configured IP. 2. The ifup process keeps running. cu also observed these process in 'Z' state Expected results: VLAN interface up with configured IP Additional info: 1. The issue not observed in RHEL 7. 2. Issue observed for VLAN interfaces. 3. Tried to reproduce it for alias interfaces (eth1:0). But was not success. Command executed successfully.