Bug 1493961 - [Docs][Upgrades] Add workaround for Cinder API service not working properly after OSP9 -> OSP10 -> OSP11 upgrade
Summary: [Docs][Upgrades] Add workaround for Cinder API service not working properly a...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 11.0 (Ocata)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ga
: 11.0 (Ocata)
Assignee: Dan Macpherson
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On: 1444643 1444866
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-21 08:34 UTC by Martin Schuppert
Modified: 2023-02-22 23:02 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1444866
Environment:
Last Closed: 2018-06-22 12:34:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Martin Schuppert 2017-09-21 08:34:39 UTC
+++ This bug was initially created as a clone of Bug #1444866 +++

The needed step got added to section '3.7. POST-UPGRADE NOTES FOR THE OVERCLOUD'
as part of the post upgrade work, but to migrate instances with cinder volume
attached off the computes we'd need to do that step right after the controller 
upgrade, or at least before '3.6.3. Upgrading Compute Nodes' where we migrate
instances off the compute

Comment 1 Martin Schuppert 2017-09-21 08:36:16 UTC
For reference this is the section from the POST-UPGRADE section:

~~~
OpenStack Block Storage (cinder) API uses a new sizelimit filter in Red Hat OpenStack Platform 11. However, following an upgrade path from OpenStack Platform 9 to OpenStack Platform 10 to OpenStack Platform 11 might not update to this new filter. Check the filter on Controller or Cinder API nodes using the following command:

$ grep filter:sizelimit /etc/cinder/api-paste.ini -A1
The filter should appear as the following:

[filter:sizelimit]
paste.filter_factory = oslo_middleware.sizelimit:RequestBodySizeLimiter.factory
If not, replace the value in the /etc/cinder/api-paste.ini file of each Controller or Cinder API node and restart the httpd service:

$ sudo sed -i s/cinder.api.middleware.sizelimit/oslo_middleware.sizelimit/ /etc/cinder/api-paste.ini
$ sudo systemctl restart httpd
~~~

Comment 2 Sofer Athlan-Guyot 2017-10-09 09:54:28 UTC
Hi,

This is fixed there https://bugzilla.redhat.com/show_bug.cgi?id=1444643 .  So this workaround is no longer needed since openstack-tripleo-heat-templates-5.3.0-2.el7ost.

Martin, is that ok or do we still need the doc workaround ?

Comment 3 Martin Schuppert 2017-10-09 13:41:58 UTC
(In reply to Sofer Athlan-Guyot from comment #2)
> Hi,
> 
> This is fixed there https://bugzilla.redhat.com/show_bug.cgi?id=1444643 . 
> So this workaround is no longer needed since
> openstack-tripleo-heat-templates-5.3.0-2.el7ost.
> 
> Martin, is that ok or do we still need the doc workaround ?

What we did:
1) performed a minor update of the OSP10 env to latest at Sep 20th. Since the
   mentioned errata got released on the 6th Sept we should have had this. I
   do not have logs to check that now.
2) update to OSP11 with openstack-tripleo-heat-templates-6.2.0-3.el7ost. This 
   should also have the fix, but we still have seen the issue and had to fix 
   /etc/cinder/api-paste.ini .

We realized it in step 3.6.3 to update the computes, and as the workaround is mentioned in the 3.7 Post-Upgrade Notes it was/is too late in the process. 

So not sure why we have seen the issue even with the fix in place. Might be 
better to keep the workaround and add move it before the upgrade of the computes?

Comment 4 Sofer Athlan-Guyot 2017-10-10 07:46:32 UTC
(In reply to Martin Schuppert from comment #3)
> (In reply to Sofer Athlan-Guyot from comment #2)
> > Hi,
> > 
> > This is fixed there https://bugzilla.redhat.com/show_bug.cgi?id=1444643 . 
> > So this workaround is no longer needed since
> > openstack-tripleo-heat-templates-5.3.0-2.el7ost.
> > 
> > Martin, is that ok or do we still need the doc workaround ?
> 
> What we did:
> 1) performed a minor update of the OSP10 env to latest at Sep 20th. Since the
>    mentioned errata got released on the 6th Sept we should have had this. I
>    do not have logs to check that now.

Hum, starting from osp10 is too late for this patch as it does not get applied during update but only during upgrade.

> 2) update to OSP11 with openstack-tripleo-heat-templates-6.2.0-3.el7ost.
> This 
>    should also have the fix, but we still have seen the issue and had to fix 
>    /etc/cinder/api-paste.ini .

So the working path is osp9 (the above patch in osp10) -> upgrade to 10.  Anything else won't work.  It doesn't do anything in osp10->11 upgrade.

> 
> We realized it in step 3.6.3 to update the computes, and as the workaround
> is mentioned in the 3.7 Post-Upgrade Notes it was/is too late in the
> process. 
> 
> So not sure why we have seen the issue even with the fix in place. Might be 
> better to keep the workaround and add move it before the upgrade of the
> computes?

The fix is only applied during osp9->10 upgrade, that's why.  The "good" workaround for osp9->10 upgrade is the one in that diff: https://review.openstack.org/#/c/459271/6/extraconfig/tasks/major_upgrade_controller_pacemaker_2.sh

Applying this will enable you to not have to constantly patch this file.  Basically to end this you have to:

 cp /etc/cinder/api-paste.ini.rpmnew /etc/cinder/api-paste.ini

As soon as you are in line with rpm then it gets updated.

So I would say that the workaround in the documentation is just asking for trouble.  This file will never be updated by rpm as it detects a modification (an added newline is enough).  For each upgrade you'll have an api-paste.ini.rpmnew file and you'll have to make some adjustment manually.

So back to the fix.  What it does is that it revert the deprecated way of setting up tls in OSP9 so that it looks like the original api-paste.ini from the package.  The normal rpm upgrade can kick in instead of having any rpmnew file created.

So back to documentation.  The best way to get this out manually is:

  diff /etc/cinder/paste-ini.conf.rpmnew /etc/cinder/paste-ini.conf

check that there is no user site modification. Then

  cp /etc/cinder/paste-ini.conf.rpmnew /etc/cinder/paste-ini.conf

And you won't be bothered anymore.

Comment 5 Martin Schuppert 2017-10-10 10:43:43 UTC
(In reply to Sofer Athlan-Guyot from comment #4)
> (In reply to Martin Schuppert from comment #3)
> > (In reply to Sofer Athlan-Guyot from comment #2)
> > > Hi,
> > > 
> > > This is fixed there https://bugzilla.redhat.com/show_bug.cgi?id=1444643 . 
> > > So this workaround is no longer needed since
> > > openstack-tripleo-heat-templates-5.3.0-2.el7ost.
> > > 
> > > Martin, is that ok or do we still need the doc workaround ?
> > 
> > What we did:
> > 1) performed a minor update of the OSP10 env to latest at Sep 20th. Since the
> >    mentioned errata got released on the 6th Sept we should have had this. I
> >    do not have logs to check that now.
> 
> Hum, starting from osp10 is too late for this patch as it does not get
> applied during update but only during upgrade.

For customers which are already on OSP10 with a version before we released
the fix, like we were here, don't we still need then the documentation to
either state the workaround we have at the moment, just at the correct step
of the doc or just make sure to copy the rpmnew :

cp /etc/cinder/paste-ini.conf.rpmnew /etc/cinder/paste-ini.conf

> 
> > 2) update to OSP11 with openstack-tripleo-heat-templates-6.2.0-3.el7ost.
> > This 
> >    should also have the fix, but we still have seen the issue and had to fix 
> >    /etc/cinder/api-paste.ini .
> 
> So the working path is osp9 (the above patch in osp10) -> upgrade to 10. 
> Anything else won't work.  It doesn't do anything in osp10->11 upgrade.
> 
> > 
> > We realized it in step 3.6.3 to update the computes, and as the workaround
> > is mentioned in the 3.7 Post-Upgrade Notes it was/is too late in the
> > process. 
> > 
> > So not sure why we have seen the issue even with the fix in place. Might be 
> > better to keep the workaround and add move it before the upgrade of the
> > computes?
> 
> The fix is only applied during osp9->10 upgrade, that's why.  The "good"
> workaround for osp9->10 upgrade is the one in that diff:
> https://review.openstack.org/#/c/459271/6/extraconfig/tasks/
> major_upgrade_controller_pacemaker_2.sh
> 
> Applying this will enable you to not have to constantly patch this file. 
> Basically to end this you have to:
> 
>  cp /etc/cinder/api-paste.ini.rpmnew /etc/cinder/api-paste.ini
> 
> As soon as you are in line with rpm then it gets updated.
> 
> So I would say that the workaround in the documentation is just asking for
> trouble.  This file will never be updated by rpm as it detects a
> modification (an added newline is enough).  For each upgrade you'll have an
> api-paste.ini.rpmnew file and you'll have to make some adjustment manually.
> 
> So back to the fix.  What it does is that it revert the deprecated way of
> setting up tls in OSP9 so that it looks like the original api-paste.ini from
> the package.  The normal rpm upgrade can kick in instead of having any
> rpmnew file created.
> 
> So back to documentation.  The best way to get this out manually is:
> 
>   diff /etc/cinder/paste-ini.conf.rpmnew /etc/cinder/paste-ini.conf
> 
> check that there is no user site modification. Then
> 
>   cp /etc/cinder/paste-ini.conf.rpmnew /etc/cinder/paste-ini.conf
> 
> And you won't be bothered anymore.

Comment 6 Sofer Athlan-Guyot 2018-01-30 10:56:55 UTC
Hi Dan,

so in "3.7. POST-UPGRADE NOTES FOR THE OVERCLOUD" of osp10 documentation could we have a note saying that cinder configuration need to be checked because of an issue before openstack-tripleo-heat-templates-5.3.0-2.el7ost.

The check being:

   diff /etc/cinder/paste-ini.conf.rpmnew /etc/cinder/paste-ini.conf

if anything appears that the user did not set up explicitly, then it has to overwrite this file to get the latest changes:

   cp /etc/cinder/paste-ini.conf.rpmnew /etc/cinder/paste-ini.conf

Comment 7 Dan Macpherson 2018-01-31 01:40:33 UTC
ACK

Comment 12 Scott Lewis 2018-06-22 12:34:29 UTC
OSP11 is now retired, see details at https://access.redhat.com/errata/product/191/ver=11/rhel---7/x86_64/RHBA-2018:1828


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