Bug 203847
Summary: | VMware e1000 adapter doesn't get an IP address assigned. Manually assigning one does not solve the issue | ||
---|---|---|---|
Product: | Networking | Reporter: | www.anuprita804 |
Component: | Other | Assignee: | Stephen Hemminger (stephen) |
Status: | RESOLVED INVALID | ||
Severity: | high | CC: | www.anuprita804 |
Priority: | P1 | ||
Hardware: | x86-64 | ||
OS: | Linux | ||
Kernel Version: | 5.2-rc3 | Subsystem: | |
Regression: | Yes | Bisected commit-id: | |
Attachments: | Dmesg for 5.2-rc3 |
Description
www.anuprita804
2019-06-07 23:53:00 UTC
Note that I'm fine with sharing the IP address of the server The "[root@archlinux ~]# ip link" line is the IP link command performed on the 5.1.7 stable kernel Stephen, any updates on this? I've been working towards bisecting it but debugging a remote server is slightly hard (7dc2bccab0ee) $ git bisect bad 7dc2bccab0ee37ac28096b8fcdc390a679a15841 is the first bad commit commit 7dc2bccab0ee37ac28096b8fcdc390a679a15841 Author: Maxim Mikityanskiy <maximmi@mellanox.com> Date: Tue May 21 06:40:04 2019 +0000 Validate required parameters in inet6_validate_link_af inet6_set_link_af requires that at least one of IFLA_INET6_TOKEN or IFLA_INET6_ADDR_GET_MODE is passed. If none of them is passed, it returns -EINVAL, which may cause do_setlink() to fail in the middle of processing other commands and give the following warning message: A link change request failed with some changes committed already. Interface eth0 may have been left with an inconsistent configuration, please check. Check the presence of at least one of them in inet6_validate_link_af to detect invalid parameters at an early stage, before do_setlink does anything. Also validate the address generation mode at an early stage. Signed-off-by: Maxim Mikityanskiy <maximmi@mellanox.com> Signed-off-by: David S. Miller <davem@davemloft.net> net/ipv6/addrconf.c | 57 ++++++++++++++++++++++++++++++++--------------------- 1 file changed, 35 insertions(+), 22 deletions(-) After a quick search for the commit sha# it seems this has been reported before here https://www.mail-archive.com/netdev@vger.kernel.org/msg300190.html https://bugzilla.kernel.org/show_bug.cgi?id=203769 https://bugzilla.redhat.com/show_bug.cgi?id=1718192 No idea. Kernel bugzilla is write only. You should contact the Intel developers. Thanks Stephen. I have mailed the people who are maintaining the affected file After rebuilding systemd from git myself the issue has been resolved Further reading makes me believe this was a systemd bug and not a kernel bug at all |