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:
When creating veth(type=veth) with ipv6 address(ipv4 is not mentioned), nmstate gets stuck for about 5 minutes and finally failed
Version-Release number of selected component (if applicable):
nmstate-1.2.1-1.el8.x86_64
nispor-1.2.3-1.el8.x86_64
NetworkManager-1.36.0-0.7.el8.x86_64
How reproducible:
100%
Steps to Reproduce:
echo "
interfaces:
- name: veth0
type: veth
state: up
ipv6:
enabled: true
address:
- ip: 2001:db8::1
prefix-length: 64
veth:
peer: veth0_p
" | nmstatectl apply -
Actual results:
The job started at 23:12:24 and failed at 23:17:25, was stuck for 5 minutes in total
/tmp/nmstatelog/2022-02-16-23:12:24-416481733.log
2022-02-16 23:17:25,076 root ERROR Rollback failed with error Activate profile uuid:3411afb4-e1ed-4943-ae04-6397af3d072d iface:veth0 type: veth failed: reason=<enum NM_ACTIVE_CONNECTION_STATE_REASON_UNKNOWN of type NM.ActiveConnectionStateReason><enum NM_DEVICE_STATE_REASON_CONNECTION_REMOVED of type NM.DeviceStateReason>
Traceback (most recent call last):
File "/usr/bin/nmstatectl", line 11, in <module>
load_entry_point('nmstate==1.2.1', 'console_scripts', 'nmstatectl')()
File "/usr/lib/python3.6/site-packages/nmstatectl/nmstatectl.py", line 74, in main
return args.func(args)
File "/usr/lib/python3.6/site-packages/nmstatectl/nmstatectl.py", line 338, in set
return apply(args)
File "/usr/lib/python3.6/site-packages/nmstatectl/nmstatectl.py", line 355, in apply
args.save_to_disk,
File "/usr/lib/python3.6/site-packages/nmstatectl/nmstatectl.py", line 419, in apply_state
save_to_disk=save_to_disk,
File "/usr/lib/python3.6/site-packages/libnmstate/netapplier.py", line 89, in apply
_apply_ifaces_state(plugins, net_state, verify_change, save_to_disk)
File "/usr/lib/python3.6/site-packages/libnmstate/netapplier.py", line 122, in _apply_ifaces_state
plugin.apply_changes(net_state, save_to_disk)
File "/usr/lib/python3.6/site-packages/libnmstate/nm/plugin.py", line 233, in apply_changes
NmProfiles(self.context).apply_config(net_state, save_to_disk)
File "/usr/lib/python3.6/site-packages/libnmstate/nm/profiles.py", line 99, in apply_config
self._ctx.wait_all_finish()
File "/usr/lib/python3.6/site-packages/libnmstate/nm/context.py", line 217, in wait_all_finish
raise tmp_error
libnmstate.error.NmstateTimeoutError: Action {'Activate profile uuid:3411afb4-e1ed-4943-ae04-6397af3d072d iface:veth0 type: veth'} timeout
/tmp/nmstatelog/2022-02-16-23:12:24-416481733.1.log nmstatectl set localroute.yaml return 1
Expected results:
No failure
Additional info:
The other related tests:
1. Use "type=ethernet": PASS
2. Use dual stack IP: PASS
3. Use ipv4 only: PASS
In case anyone cares:
Root cause, NetworkManager is waiting link carrier, but its veth peer is
not activated yet, hence the link carrier is stuck to DOWN.
To fix this issue, do grouping activation on veth and its peer, the
activation retry will retry on veth once its peer activated and UP.
The rust code does not have this problem as rust is doing grouping activation for veth.
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 (nmstate bug fix and enhancement update), 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-2022:7465
Description of problem: When creating veth(type=veth) with ipv6 address(ipv4 is not mentioned), nmstate gets stuck for about 5 minutes and finally failed Version-Release number of selected component (if applicable): nmstate-1.2.1-1.el8.x86_64 nispor-1.2.3-1.el8.x86_64 NetworkManager-1.36.0-0.7.el8.x86_64 How reproducible: 100% Steps to Reproduce: echo " interfaces: - name: veth0 type: veth state: up ipv6: enabled: true address: - ip: 2001:db8::1 prefix-length: 64 veth: peer: veth0_p " | nmstatectl apply - Actual results: The job started at 23:12:24 and failed at 23:17:25, was stuck for 5 minutes in total /tmp/nmstatelog/2022-02-16-23:12:24-416481733.log 2022-02-16 23:17:25,076 root ERROR Rollback failed with error Activate profile uuid:3411afb4-e1ed-4943-ae04-6397af3d072d iface:veth0 type: veth failed: reason=<enum NM_ACTIVE_CONNECTION_STATE_REASON_UNKNOWN of type NM.ActiveConnectionStateReason><enum NM_DEVICE_STATE_REASON_CONNECTION_REMOVED of type NM.DeviceStateReason> Traceback (most recent call last): File "/usr/bin/nmstatectl", line 11, in <module> load_entry_point('nmstate==1.2.1', 'console_scripts', 'nmstatectl')() File "/usr/lib/python3.6/site-packages/nmstatectl/nmstatectl.py", line 74, in main return args.func(args) File "/usr/lib/python3.6/site-packages/nmstatectl/nmstatectl.py", line 338, in set return apply(args) File "/usr/lib/python3.6/site-packages/nmstatectl/nmstatectl.py", line 355, in apply args.save_to_disk, File "/usr/lib/python3.6/site-packages/nmstatectl/nmstatectl.py", line 419, in apply_state save_to_disk=save_to_disk, File "/usr/lib/python3.6/site-packages/libnmstate/netapplier.py", line 89, in apply _apply_ifaces_state(plugins, net_state, verify_change, save_to_disk) File "/usr/lib/python3.6/site-packages/libnmstate/netapplier.py", line 122, in _apply_ifaces_state plugin.apply_changes(net_state, save_to_disk) File "/usr/lib/python3.6/site-packages/libnmstate/nm/plugin.py", line 233, in apply_changes NmProfiles(self.context).apply_config(net_state, save_to_disk) File "/usr/lib/python3.6/site-packages/libnmstate/nm/profiles.py", line 99, in apply_config self._ctx.wait_all_finish() File "/usr/lib/python3.6/site-packages/libnmstate/nm/context.py", line 217, in wait_all_finish raise tmp_error libnmstate.error.NmstateTimeoutError: Action {'Activate profile uuid:3411afb4-e1ed-4943-ae04-6397af3d072d iface:veth0 type: veth'} timeout /tmp/nmstatelog/2022-02-16-23:12:24-416481733.1.log nmstatectl set localroute.yaml return 1 Expected results: No failure Additional info: The other related tests: 1. Use "type=ethernet": PASS 2. Use dual stack IP: PASS 3. Use ipv4 only: PASS