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.
DescriptionEdouard Bourguignon
2016-10-26 09:57:09 UTC
Description of problem:
We have a server with 2000 vlan interfaces. When we manualy start the systemd-networkd service, everything works fine.
But, at boot, the same service randomly configure only aroud 1400 interfaces. The others stay in pending state for ever (as shown with networkctl). Restarting systemd-networkd fix this.
Version-Release number of selected component (if applicable):
systemd-networkd-219-19.el7_2.13.x86_64
How reproducible:
static
Steps to Reproduce:
1. Have an ethernet interface, let say ens6
2. Configure /etc/systemd/network/ens6.network with
[Match]
Name=ens6
[Network]
VLAN=vlan1
VLAN=vlan2
...
VLAN=vlan2000
3. Configure each /etc/systemd/network/vlanX.netdev with
[NetDev]
Name=vlanX
Kind=vlan
[VLAN]
Id=X
4. Configure each /etc/systemd/network/vlanX.network with
[Match]
Name=vlanX
[Address]
Address=172.A.B.C/32
5. systemctl retart systemd-networkd brings the 2000 interfaces and their IP
6. reboot and do ip a|grep "172\.16"|wc -l (aroud 1400). All vlan interfaces are up, but not all the IP are set. Command networkctl shows interfaces in pending state. Nothing happens next.
7. systemctl restart systemd-networkd fix the problem after boot.
Actual results:
systemctl restart systemd-networkd works
Same service at boot, doesn't works for all the interfaces
Expected results:
should work the same. No interface in pending state for ever.
Additional info:
works (kind of) with classical "network" service, but takes 85 minutes to boot...
We tried some parameters in system.conf about timeout, but no luck. Is there something wrong ?
Well we don't support systemd-networkd in rhel7. But could you please try the same thing on some newer fedora? If this was fixed in ustream then maybe we could find a fix and backport it to rhel/centos.
With the initscripts, have you tried to put ARPCHECK=no to the ifcfg files?