Bug 1833493 - openvswitch2.11 replaces /etc/logrotate.d/openvswitch with the new one after updating RHOSP13 from z9 to z10
Summary: openvswitch2.11 replaces /etc/logrotate.d/openvswitch with the new one after ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 15.0 (Stein)
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: async
: 15.0 (Stein)
Assignee: Greg Rakauskas
QA Contact: RHOS Documentation Team
URL:
Whiteboard: docs-accepted
Depends On: 1805103
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-08 18:11 UTC by Greg Rakauskas
Modified: 2020-05-08 18:18 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1805103
Environment:
Last Closed: 2020-05-08 18:18:41 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 1 Greg Rakauskas 2020-05-08 18:18:41 UTC 
Hi,

The following fix added to the RHOSP 15, "Upgrading Red Hat OpenStack Platform" 
guide:

   During updates, if the Open vSwitch (OVS) major version changes (for example,
   2.9 to 2.11), director renames any user-customized configuration files with 
   an .rpmsave extension, and installs the default OVS configuration.

   If you want to retain your earlier OVS customizations, you must manually 
   reapply your modifications contained in the renamed files (for example, 
   logrotate configurations in /etc/logrotate.d/openvswitch). This two-step
   update method avoids data plane interruptions that would be triggered by an
   automatic RPM package update.

Customers can now see this content on the Red Hat Cudtomer Portal, here:

   https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/15/html-single/upgrading_red_hat_openstack_platform/index#before-starting-the-upgrade

Thanks,
--Greg
Note You need to log in before you can comment on or make changes to this bug.