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 1915850 - Rollback not working with a linux-bridge on default bridge at OCP with OVN Kubernetes
Summary: Rollback not working with a linux-bridge on default bridge at OCP with OVN Ku...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: nmstate
Version: 8.3
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: 8.0
Assignee: Gris Ge
QA Contact: Mingyu Shi
URL:
Whiteboard:
Depends On:
Blocks: 1896469
TreeView+ depends on / blocked
 
Reported: 2021-01-13 14:36 UTC by Quique Llorente
Modified: 2023-12-26 04:47 UTC (History)
7 users (show)

Fixed In Version: nmstate-1.1.0-0.1.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-09 17:42:57 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
State to set (122 bytes, text/plain)
2021-01-13 14:36 UTC, Quique Llorente 		no flags Details
NetworkManager debug logs (1.71 MB, application/gzip)
2021-01-13 14:41 UTC, Quique Llorente 		no flags Details
show state before set (6.02 KB, text/plain)
2021-01-13 14:41 UTC, Quique Llorente 		no flags Details
show state after set (7.07 KB, text/plain)
2021-01-13 14:42 UTC, Quique Llorente 		no flags Details
show state after rollback (6.62 KB, text/plain)
2021-01-13 14:42 UTC, Quique Llorente 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1896469 0 unspecified CLOSED In cluster with OVN Kubernetes networking - a node doesn't recover when configuring linux-bridge over its default NIC 2021-11-02 15:58:40 UTC
Red Hat Issue Tracker NMT-1011 0 None None None 2023-12-26 04:47:13 UTC
Red Hat Product Errata RHBA-2021:4157 0 None None None 2021-11-09 17:43:13 UTC

Description Quique 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:
Comment 1 Quique Llorente 2021-01-13 14:41:31 UTC 
Created attachment 1747089 [details]
NetworkManager debug logs
Comment 2 Quique Llorente 2021-01-13 14:41:58 UTC 
Created attachment 1747090 [details]
show state before set
Comment 3 Quique Llorente 2021-01-13 14:42:22 UTC 
Created attachment 1747091 [details]
show state after set
Comment 4 Quique Llorente 2021-01-13 14:42:44 UTC 
Created attachment 1747092 [details]
show state after rollback
Comment 5 Petr Horáček 2021-02-01 13:49:47 UTC 
Gris, would you please prioritize it? Would it make it to 1.0?
Comment 6 Gris Ge 2021-02-02 10:37:20 UTC 
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 7 Fernando 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!
Comment 8 Quique Llorente 2021-05-06 13:33:29 UTC 
@ferferna now it's easier with the nmstate/automation we have for k8s I will give it a try.
Comment 9 Quique Llorente 2021-06-02 05:47:58 UTC 
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
Comment 10 Till Maas 2021-06-02 07:34:36 UTC 
(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?
Comment 11 Gris Ge 2021-06-02 08:27:14 UTC 
Reporter(Quique Llorente) agree on bug closure.

But let's keep this bug for QE or devel effort to create auto test case for this.
Comment 15 Mingyu Shi 2021-06-20 05:49:23 UTC 
As it works on nmstate-1.0 and above, mark as verified
Comment 17 errata-xmlrpc 2021-11-09 17:42:57 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:4157
Note You need to log in before you can comment on or make changes to this bug.