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.

Bug 1915631

Summary: failed to take a veth up and attach it to a vrf at the same time
Product: Red Hat Enterprise Linux 8 Reporter: Mingyu Shi <mshi>
Component: nmstateAssignee: Fernando F. Mancera <ferferna>
Status: CLOSED ERRATA QA Contact: Mingyu Shi <mshi>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.4CC: ferferna, jiji, jishi, network-qe, till
Target Milestone: rcKeywords: Triaged
Target Release: 8.4Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-18 15:18:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
beaker.log none

Description Mingyu Shi 2021-01-13 05:34:55 UTC
Description of problem:
Failed to take a veth up(here 'up' means creating an NM profile, not real link state up) and attach it to a vrf at the same time.
It works well on other main port types(bond, team, bridge, ovs), but only vrf.

Version-Release number of selected component (if applicable):
nmstate-1.0.1-0.1.el8.noarch
nispor-1.0.1-2.el8.x86_64
NetworkManager-1.30.0-0.5.el8.x86_64

How reproducible:
100%

Steps to Reproduce:
nmcli con del veth0
ip link del veth0
ip link add veth0  type veth peer veth0_ep
ip link set veth0 up
cat << EOF > vrf0.yaml
interfaces:
# vrf
- name: vrf0
  type: vrf
  state: up
  vrf:
    port:
    - veth0
    route-table-id: 1000
- {name: veth0, type: ethernet, state: up}
EOF

nmstatectl set vrf0.yaml #failed at 1st time
nmstatectl set vrf0.yaml #works at 2nd time

Actual results:
failed at 1st time

Expected results:
no failure

Additional info:
Traceback (most recent call last):
  File "/usr/bin/nmstatectl", line 11, in <module>
    load_entry_point('nmstate==1.0.1', 'console_scripts', 'nmstatectl')()
  File "/usr/lib/python3.6/site-packages/nmstatectl/nmstatectl.py", line 70, in main
    return args.func(args)
  File "/usr/lib/python3.6/site-packages/nmstatectl/nmstatectl.py", line 289, in apply
    args.save_to_disk,
  File "/usr/lib/python3.6/site-packages/nmstatectl/nmstatectl.py", line 329, in apply_state
    save_to_disk=save_to_disk,
  File "/usr/lib/python3.6/site-packages/libnmstate/netapplier.py", line 71, in apply
    _apply_ifaces_state(plugins, net_state, verify_change, save_to_disk)
  File "/usr/lib/python3.6/site-packages/libnmstate/netapplier.py", line 104, in _apply_ifaces_state
    plugin.apply_changes(net_state, save_to_disk)
  File "/usr/lib/python3.6/site-packages/libnmstate/nm/plugin.py", line 323, 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 59, in apply_config
    self._ctx.wait_all_finish()
  File "/usr/lib/python3.6/site-packages/libnmstate/nm/context.py", line 222, in wait_all_finish
    raise tmp_error
libnmstate.error.NmstateLibnmError: Activate profile uuid:d8d7b15a-01d8-4e70-b15f-8c2f08fd03a6 iface:veth0 type: ethernet failed: reason=<enum NM_ACTIVE_CONNECTION_STATE_REASON_DEVICE_DISCONNECTED of type NM.ActiveConnectionStateReason> <enum NM_DEVICE_STATE_REASON_IP_CONFIG_UNAVAILABLE of type NM.DeviceStateReason>

Comment 1 Mingyu Shi 2021-01-13 10:16:30 UTC
Correct the reproducer:

nmcli con del veth0
ip link del veth0
ip link add veth0 type veth peer veth0_ep
ip link set veth0 up
#add the command below
ip link set veth0_ep up
cat << EOF > vrf0.yaml
interfaces:
# vrf
- name: vrf0
  type: vrf
  state: up
  vrf:
    port:
    - veth0
    route-table-id: 1000
- {name: veth0, type: ethernet, state: up}
EOF
 
nmstatectl set vrf0.yaml

Comment 2 Fernando F. Mancera 2021-01-13 15:18:11 UTC
This is fixed with the recent changes on profile activation. An integration test has been proposed for upstream in https://github.com/nmstate/nmstate/pull/1469.

Comment 3 Mingyu Shi 2021-01-18 11:40:18 UTC
Verified with versions:
nmstate-1.0.1-0.20210115115643933056.pr1478.27.gc9b2298.el8.noarch
nispor-1.0.1-2.el8.x86_64
NetworkManager-1.30.0-0.5.el8.x86_64

Comment 4 Mingyu Shi 2021-01-18 11:41:43 UTC
Created attachment 1748435 [details]
beaker.log

Comment 7 Mingyu Shi 2021-01-20 03:07:34 UTC
Verified with versions:
nmstate-1.0.1-1.el8.noarch
nispor-1.0.1-2.el8.x86_64
NetworkManager-1.30.0-0.5.el8.x86_64

PASS.

Comment 9 errata-xmlrpc 2021-05-18 15:18:22 UTC
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-2021:1748