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 create a bridge or bond, might got failure like said slave
interface DEVICE_DISCONNECTED.
Version-Release number of selected component (if applicable):
nmstate-0.0.8-3.el8
How reproducible:
1 out of 1000 or worse
Steps to Reproduce:
* Download attached yaml files and run below commands:
for x in `seq 1 1000`; do
sudo ncl set eth1_up.yml && \
sudo ncl set br0_up.yml && \
sudo nmcli c del br0 eth1 && sleep 1 || break;
echo $x;
done
Actual results:
Got failure said activation failed with reason DEVICE_DISCONNECTED
Expected results:
all pass
Additional info:
I hit this problem after 454 retry.
(In reply to Gris Ge from comment #3)
> This problem also exists when configuring static IPv6 address with routes.
This is not caused by this bug. Please ignore.
[root@ibm-x3650m4-02 ~]0# uname -a
Linux ibm-x3650m4-02.rhts.eng.pek2.redhat.com 4.18.0-141.el8.x86_64 #1 SMP Fri Aug 30 15:27:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
[root@ibm-x3650m4-02 ~]0# rpm -q nmstate
nmstate-0.0.8-12.el8.noarch
[root@ibm-x3650m4-02 ~]0# cat eth1_up.yml
---
interfaces:
- name: eth1
type: ethernet
state: up
[root@ibm-x3650m4-02 ~]0# cat br0_up.yml
---
interfaces:
- name: eth1
type: ethernet
state: up
- name: br0
type: linux-bridge
state: up
bridge:
port:
- name: eth1
# run script below:
for x in `seq 1 1000`; do
nmstatectl set eth1_up.yml && \
nmstatectl set br0_up.yml && \
nmcli c del br0 eth1 && sleep 1 || break;
echo $x;
done
I've done twice, no reproduction in both new and old version. Will cover it by automation.
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.
https://access.redhat.com/errata/RHBA-2019:3347
Description of problem: When create a bridge or bond, might got failure like said slave interface DEVICE_DISCONNECTED. Version-Release number of selected component (if applicable): nmstate-0.0.8-3.el8 How reproducible: 1 out of 1000 or worse Steps to Reproduce: * Download attached yaml files and run below commands: for x in `seq 1 1000`; do sudo ncl set eth1_up.yml && \ sudo ncl set br0_up.yml && \ sudo nmcli c del br0 eth1 && sleep 1 || break; echo $x; done Actual results: Got failure said activation failed with reason DEVICE_DISCONNECTED Expected results: all pass Additional info: I hit this problem after 454 retry.