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 1419159 - RHEL 7 upgrading openvswitch version 2.4 -> 2.5 causes OVS interfaces to lose IP addresses
Summary: RHEL 7 upgrading openvswitch version 2.4 -> 2.5 causes OVS interfaces to lose...
Keywords:
Status: CLOSED DUPLICATE of bug 1397045
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: openvswitch
Version: 7.3
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Open vSwitch development team
QA Contact: ovs-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-03 18:05 UTC by Matt Flusche
Modified: 2020-12-14 08:08 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-07 21:43:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Matt Flusche 2017-02-03 18:05:56 UTC 
Description of problem:

A yum upgrade of the openvswitch package from 2.4 -> 2.4 causes OVS interfaces to lose IP addresses.

Ran into this issue while upgrading all packages from 7.2 -> 7.3.  Narrowed the issue down to just the openvswitch package.

Version-Release number of selected component (if applicable):

openvswitch-2.5.0-14.git20160727.el7fdp.x86_64

How reproducible:
100% so far


Steps to Reproduce:
upgrade openvswitch package.

In this environment I have two OVS interfaces with addresses assigned.

[root@overcloud-controller-0 ~]# ip a ls br-ex
16: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN 
    link/ether 52:54:00:b7:9f:2d brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.132/24 brd 192.168.0.255 scope global br-ex
       valid_lft forever preferred_lft forever
    inet6 fe80::5054:ff:feb7:9f2d/64 scope link 
       valid_lft forever preferred_lft forever


[root@overcloud-controller-0 ~]# ip a ls vlan5
18: vlan5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN 
    link/ether 2a:de:c0:f3:e6:56 brd ff:ff:ff:ff:ff:ff
    inet 192.168.2.81/24 brd 192.168.2.255 scope global vlan5
       valid_lft forever preferred_lft forever
    inet 192.168.2.80/32 brd 192.168.2.255 scope global vlan5
       valid_lft forever preferred_lft forever
    inet6 fe80::28de:c0ff:fef3:e656/64 scope link 
       valid_lft forever preferred_lft forever


Version of OVS before:

[root@overcloud-controller-0 ~]# rpm -q openvswitch
openvswitch-2.4.0-2.el7_2.x86_64

Update:

[root@overcloud-controller-0 ~]# yum -y update openvswitch

...
Updated:
  openvswitch.x86_64 0:2.5.0-14.git20160727.el7fdp                                                                                    

Complete!

OVS interfaces are now missing addresses:

[root@overcloud-controller-0 ~]# ip a ls br-ex
23: br-ex: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN 
    link/ether 52:54:00:b7:9f:2d brd ff:ff:ff:ff:ff:ff

[root@overcloud-controller-0 ~]# ip a ls vlan5
24: vlan5: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN 
    link/ether 16:e8:16:88:26:ac brd ff:ff:ff:ff:ff:ff


ifup will bring them back online:

[root@overcloud-controller-0 ~]# ifup br-ex
[root@overcloud-controller-0 ~]# ifup vlan5

[root@overcloud-controller-0 ~]# ip a ls br-ex
23: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN 
    link/ether 52:54:00:b7:9f:2d brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.132/24 brd 192.168.0.255 scope global br-ex
       valid_lft forever preferred_lft forever
    inet6 fe80::5054:ff:feb7:9f2d/64 scope link 
       valid_lft forever preferred_lft forever

[root@overcloud-controller-0 ~]# ip a ls vlan5
24: vlan5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN 
    link/ether 16:e8:16:88:26:ac brd ff:ff:ff:ff:ff:ff
    inet 192.168.2.81/24 brd 192.168.2.255 scope global vlan5
       valid_lft forever preferred_lft forever
    inet6 fe80::14e8:16ff:fe88:26ac/64 scope link 
       valid_lft forever preferred_lft forever



Actual results:
IP addresses missing after patch.

Expected results:
OVS networking to function the same as before the update

Additional info:

Initially we thought this was related to other package update BZs:
NetworkManager
https://bugzilla.redhat.com/show_bug.cgi?id=1367580
initscripts
https://bugzilla.redhat.com/show_bug.cgi?id=1366348

I tested those updates and they didn't break this environment.
Comment 3 Flavio Leitner 2017-02-07 21:18:34 UTC 
The installed OVS 2.4 package restarts the service during the upgrade (%postun) and while doing it, it will destroy internal ports like br-ex and add a fresh one.  Unfortunately, there is no notification system to restore the networking configuration for those devices that OVS could make use of it.

We have fixed OVS 2.5 package (openvswitch-2.5.0-23.git20160727.el7fdp) to not restart the service during the upgrade or to make sure the service is not broken after the upgrade, but the recommended way is to restart the whole networking after upgrading OVS package.

See bz#1403958 and bz#1397045.
Comment 4 Matt Flusche 2017-02-07 21:43:30 UTC 
Hi Flavio,

Thanks for the follow up.  I wasn't aware that a work-around was introduced into a new version of the OSP Director heat templates to deal with this.  https://bugzilla.redhat.com/show_bug.cgi?id=1388546.  I was testing with an old version.  I will close this as a duplicate.

Thanks,

Matt

*** This bug has been marked as a duplicate of bug 1397045 ***
Note You need to log in before you can comment on or make changes to this bug.