diff options
| author |   Jenkins <jenkins@review.openstack.org> | 2017-04-06 10:35:52 +0000 |
|---|---|---|
| committer |   Gerrit Code Review <review@openstack.org> | 2017-04-06 10:35:52 +0000 |
| commit | 4fb4cc780db09d516f185b3bb0f354e226818495 (patch) | |
| tree | ea052fdf3b4bcad6beb5f7100d992059f9ef22b9 /releasenotes/notes | |
| parent | 4ddfe417754de3fb123303ede207dd25418428ad (diff) | |
| parent | d2d319ec0ead06b860f8464b001048fb4f723788 (diff) | |
Merge "Add manual ovs upgrade script for workaround ovs upgrade issue"
Diffstat (limited to 'releasenotes/notes')
| -rw-r--r-- | releasenotes/notes/ovs-2.5-2.6-composable-upgrades-workaround-73f4e56127c910b4.yaml | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/releasenotes/notes/ovs-2.5-2.6-composable-upgrades-workaround-73f4e56127c910b4.yaml b/releasenotes/notes/ovs-2.5-2.6-composable-upgrades-workaround-73f4e56127c910b4.yaml new file mode 100644 index 00000000..8c210823 --- /dev/null +++ b/releasenotes/notes/ovs-2.5-2.6-composable-upgrades-workaround-73f4e56127c910b4.yaml @@ -0,0 +1,12 @@ +--- +issues: + - During the ovs upgrade for 2.5 to 2.6 we need to workaround the classic + yum update command by handling the upgrade of the package separately to not + loose the IPs and the connectivity on the nodes. The workaround is + discussed here https://bugs.launchpad.net/tripleo/+bug/1669714 +upgrade: + - The upgrade from openvswitch 2.5 to 2.6 is handled gracefully and there should + be no user impact in particular no restart of the openvswitch service. For more + information please see the related bug above which also links the relevant code reviews. + The workaround (transparent to the user/doesn't require any input) is to download the OVS + package and install with --nopostun and --notriggerun options provided by the rpm binary. |