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.
DescriptionQuique Llorente
2021-01-13 14:36:10 UTC
Created attachment 1747088[details]
State to set
Description of problem:
At a OCP 4.7 cluster using nmstate 0.3.4 to create a linux-bridge in top of primary nic "ens3" and rolling it back fails at rolling it back and make the node connectivity being lost.
The OCP cluster is using OVN Kubernetes and the ens3 is already a slave under a ovs bridge "br-ext", issue is that rollback is not able to recover from the issue.
Version-Release number of selected component (if applicable):
nmstate 0.3.4-17
How reproducible:
ssh into a OCP 4.7 worker and set a password for root since we need to access to it using libvirt console or openstack console.
Then access to the worker using libvirt/openstack commands since connectivity is going to be lost ssh connection is broken.
Steps to Reproduce:
1. ping www.redhat.com
2. ./nmstatectl.sh set --no-commit --timeout 120 /quique/state.yaml
3. ping www.redhat.com (Connectivity is lost)
4. ./nmstatectl.sh rollback
5. ping www.redhat.com (Connectivity still lost)
Actual results:
nmstate is not able to rollback this configuration
Expected results:
nmstate restoring network configuration so we don't lose connectivity.
Additional info:
Hi Quique,
If we are expecting fix in nmstate 1.0, could you try it on nmstate-1.0(RHEL 8.4)?
In my VM, it seems works well.
Comment 7Fernando F. Mancera
2021-05-06 13:24:01 UTC
(In reply to Gris Ge from comment #6)
> Hi Quique,
>
> If we are expecting fix in nmstate 1.0, could you try it on nmstate-1.0(RHEL
> 8.4)?
>
> In my VM, it seems works well.
Please, let us know if this works on nmstate 1.0 or greater. It works well for me. Thanks!
I have test it with CNV 4.8 and at a OVNKubernetes openshift cluster and now the rollback works fine creating a linux bridge with one of the ports matcing the br-ex primary nic port.
root@zeus12 quique]# oc exec -n openshift-cnv nmstate-handler-jrpdd -- rpm -qa |grep nmstate
nmstate-1.0.2-5.el8.noarch
python3-libnmstate-1.0.2-5.el8.noarch
(In reply to Quique Llorente from comment #9)
> I have test it with CNV 4.8 and at a OVNKubernetes openshift cluster and now
> the rollback works fine creating a linux bridge with one of the ports
> matcing the br-ex primary nic port.
>
> root@zeus12 quique]# oc exec -n openshift-cnv nmstate-handler-jrpdd -- rpm
> -qa |grep nmstate
> nmstate-1.0.2-5.el8.noarch
> python3-libnmstate-1.0.2-5.el8.noarch
If it works, what are your expectations to happen here?
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:4157
Created attachment 1747088 [details] State to set Description of problem: At a OCP 4.7 cluster using nmstate 0.3.4 to create a linux-bridge in top of primary nic "ens3" and rolling it back fails at rolling it back and make the node connectivity being lost. The OCP cluster is using OVN Kubernetes and the ens3 is already a slave under a ovs bridge "br-ext", issue is that rollback is not able to recover from the issue. Version-Release number of selected component (if applicable): nmstate 0.3.4-17 How reproducible: ssh into a OCP 4.7 worker and set a password for root since we need to access to it using libvirt console or openstack console. Then access to the worker using libvirt/openstack commands since connectivity is going to be lost ssh connection is broken. Steps to Reproduce: 1. ping www.redhat.com 2. ./nmstatectl.sh set --no-commit --timeout 120 /quique/state.yaml 3. ping www.redhat.com (Connectivity is lost) 4. ./nmstatectl.sh rollback 5. ping www.redhat.com (Connectivity still lost) Actual results: nmstate is not able to rollback this configuration Expected results: nmstate restoring network configuration so we don't lose connectivity. Additional info: