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.
Created attachment 1733759[details]
log
Description of problem:
Applying route rules with the same yaml file, sometimes failed.
Version-Release number of selected component (if applicable):
nmstate-1.0.0-0.1.el8.noarch
nispor-1.0.1-2.el8.x86_64
NetworkManager-1.30.0-0.2.el8.x86_64
DISTRO=RHEL-8.4.0-20201121.d.2
Linux hpe-dl380pgen8-02-vm-15.hpe2.lab.eng.bos.redhat.com 4.18.0-250.el8.dt4.x86_64 #1 SMP Sat Nov 21 03:48:46 EST 2020 x86_64 x86_64 x86_64 GNU/Linux
How reproducible:
about 70%
Steps to Reproduce:
1.
echo "---
interfaces:
- name: dummy0
type: dummy
state: up
ipv4:
address:
- ip: 10.1.1.1
prefix-length: 24
enabled: true
route-rules:
config:
- priority: 1000
route-table: 50
ip-to: 8.8.8.8/24
ip-from: 3.3.3.3/24
- priority: 1000
route-table: 50
ip-to: 8.8.8.8/24
- priority: 1000
route-table: 50
ip-from: 3.3.3.3/24
routes:
config:
- destination: 0.0.0.0/0
metric: 150
next-hop-address: 10.1.1.254
next-hop-interface: dummy0
table-id: 50" | nmstatectl set
2. # if it is successful, remove dummy0 and repeat step 1
echo "interfaces:
- name: dummy0
state: absent" | nmstatectl set
3.
Actual results:
Sometimes failed
Expected results:
Success
Additional info:
In the attachment, I tried 4 times and only the last one got success.
Created attachment 1733759 [details] log Description of problem: Applying route rules with the same yaml file, sometimes failed. Version-Release number of selected component (if applicable): nmstate-1.0.0-0.1.el8.noarch nispor-1.0.1-2.el8.x86_64 NetworkManager-1.30.0-0.2.el8.x86_64 DISTRO=RHEL-8.4.0-20201121.d.2 Linux hpe-dl380pgen8-02-vm-15.hpe2.lab.eng.bos.redhat.com 4.18.0-250.el8.dt4.x86_64 #1 SMP Sat Nov 21 03:48:46 EST 2020 x86_64 x86_64 x86_64 GNU/Linux How reproducible: about 70% Steps to Reproduce: 1. echo "--- interfaces: - name: dummy0 type: dummy state: up ipv4: address: - ip: 10.1.1.1 prefix-length: 24 enabled: true route-rules: config: - priority: 1000 route-table: 50 ip-to: 8.8.8.8/24 ip-from: 3.3.3.3/24 - priority: 1000 route-table: 50 ip-to: 8.8.8.8/24 - priority: 1000 route-table: 50 ip-from: 3.3.3.3/24 routes: config: - destination: 0.0.0.0/0 metric: 150 next-hop-address: 10.1.1.254 next-hop-interface: dummy0 table-id: 50" | nmstatectl set 2. # if it is successful, remove dummy0 and repeat step 1 echo "interfaces: - name: dummy0 state: absent" | nmstatectl set 3. Actual results: Sometimes failed Expected results: Success Additional info: In the attachment, I tried 4 times and only the last one got success.