Created attachment 1163599 [details]
script with commands for creating VLAN subiface and assignin addresses
Description of problem:
When we try to create new VLAN subinterface and assign IPv6 address (both actions with ip command) immediately after creation, IPv6 address is not assigned. But when we stop NetworkManager, it works correctly. IPv4 addresses work fine with both NM on and off.
Version-Release number of selected component (if applicable):
Bare RHEL7.2 Server installation, run script with commands containing creation of VLAN subinterface and assigning IPv6 address to it
Steps to Reproduce:
1. Download and modify attached script (replace card name)
2. Run attached script
3. Run ip a to verify results
IPv6 address IS NOT assigned on the interface p5p1.10_0
IPv6 address IS assigned on the interface p5p1.10_0
It is not reproducible on VM
We are using NM with option no-auto-default=* in /etc/NetworkManager/NetworkManager.conf, but this shouldn't have any affect (I tried it with and without the option)
$ ethtool -i p5p1
this is probably due to NetworkManager setting IPv6 addrgenmode to none.
You can verify the addrgenmode with `ip -d link` (provided that your iproute2 version supports that).
I was unable to reproduce the issue with NetworkManager master and with rhel-7.2 (1.0.6-30).
Could you attach a logfile of NetworkManager with debug logging enabled?
Created attachment 1177241 [details]
Attached is logfile from NM with trace logging level.
Kernel version is -327, NM version is 1.0.6-27.el7
Logfile contains log from this command output:
./script.sh && sleep 1 && ip a && sleep 1 && ip link del p5p1.10_0
where script.sh is script attached to this BZ.
as you asked me on IRC, I did try to reproduce bug with recent rhel-7.3 build and newer NetworkManager. With the same steps I did not manage to reproduce the bug, it looks like it's been fixed.
kernel version: 3.10.0-461.el7.x86_64
NetworkManager version: 1.4.0-0.2.git20160621.072358da.el7
I think we can move the bug to MODIFIED than as the fix has already been included in latest NM for RHEL 7.3.
according to comment #4 moving to verified
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.