Bug 1712421 - Deployment with octavia fails when using cinder as a backend for glance
Summary: Deployment with octavia fails when using cinder as a backend for glance
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ga
: 16.2 (Train on RHEL 8.4)
Assignee: Brent Eagles
QA Contact: Arik Chernetsky
URL:
Whiteboard:
: 1888413 (view as bug list)
Depends On:
Blocks: 1904971 1955186
TreeView+ depends on / blocked
 
Reported: 2019-05-21 13:16 UTC by ojanas
Modified: 2024-03-25 15:18 UTC (History)
29 users (show)

Fixed In Version: openstack-tripleo-heat-templates-11.5.1-2.20210501015817.28ae385.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1955186 (view as bug list)
Environment:
Last Closed: 2021-09-15 07:07:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1914059 0 None None None 2021-02-01 14:22:18 UTC
OpenStack gerrit 759276 0 None MERGED Switch Octavia external tasks to 'post deploy' 2021-03-24 15:35:32 UTC
OpenStack gerrit 788505 0 None NEW Switch Octavia external tasks to 'post deploy' 2021-04-28 14:56:28 UTC
Red Hat Product Errata RHEA-2021:3483 0 None None None 2021-09-15 07:08:28 UTC

Comment 7 Giulio Fidente 2019-06-19 13:15:56 UTC
I think this was fixed by BZ #1613474 ; make sure the changes from https://review.opendev.org/#/c/604734/ are included in the copy of the templates you are using when deploying.

Comment 18 Giulio Fidente 2019-08-21 11:50:51 UTC
We reviewed the code with Carlos; Octavia should be triggering the image upload in glance after [1] cinder-volume gets configured [2] and in fact we don't see this issue in CI.

Is it possible some additional steps needed to configure the cinder EMC backend are executed too late in the process? OSP Director is really only configuring the additional backend in cinder.conf with [3] and [4], is that all what is needed for the cinder-volume instance to connect to the storage and report capabilities?

1. https://github.com/openstack/tripleo-heat-templates/blob/stable/rocky/docker/services/octavia/octavia-deployment-config.yaml#L223
2. https://github.com/openstack/puppet-tripleo/blob/stable/rocky/manifests/profile/base/cinder/volume.pp#L116
3. https://github.com/openstack/puppet-tripleo/blob/stable/rocky/manifests/profile/base/cinder/volume/dellemc_unity.pp
4. https://github.com/openstack/puppet-cinder/blob/stable/rocky/manifests/backend/dellemc_unity.pp

Comment 19 Giulio Fidente 2019-09-18 16:11:36 UTC
In contrast with what I said in comment #18 , I think we might have a real issue here because when cinder-volume is managed by pacemaker we postpone its startup to step 5 (insted of step 4) which is the same step during which octavia will try to upload the glance image ... potentially before cinder-volume is actually up and running

Need help from DF and probably PIDONE experts

Comment 21 Brent Eagles 2019-09-18 16:46:56 UTC
With respect to Giulio's comments in c19. As I understand it, the external deploy tasks/workflow tasks run before the usual configuration steps. If that is correct, then running cinder-volume in step 5 will cause the glance image upload performed by the octavia external deploy tasks to fail

Comment 22 Alex Schultz 2019-09-19 14:08:23 UTC
I believe that external/workflow tasks are also step aware. e.g. in OSP13, ceph runs in external workflow step 2.  So if there's an ordering thing with pacemaker/cinder then octavia needs to handle things in a later step or we need to evaluate if we can move cinder volume up.

Comment 23 Brent Eagles 2019-09-25 14:46:39 UTC
IIRC, the external deploy tasks run before the other tasks for a given step. Octavia external deploy steps are at step 5 so if we need to run these steps later are we looking at adding another step?

Comment 24 Alex Schultz 2019-09-25 14:51:47 UTC
We're currently not investigating adding more steps. In looking in OSP14 code, we do have an external_post_deploy_steps_tasks which run last. Perhaps you could use that?

Comment 25 Brent Eagles 2019-11-07 13:33:29 UTC
Thanks Alex. I'll see if that will do the job.

Comment 28 Brent Eagles 2020-01-21 17:55:10 UTC
This is a work in progress. The external post deploy tasks stage of deployment is a logical place to do this but we need to refactor the ansible code so the image upload can be deferred to external_post_deploy|update|upgrade_tasks.

Comment 31 Nilesh 2020-10-15 07:07:47 UTC
*** Bug 1888413 has been marked as a duplicate of this bug. ***

Comment 39 Cyril Roelandt 2020-12-10 03:34:19 UTC
@David: Yes, it seems to affect RHOSP13 as well, see https://bugzilla.redhat.com/show_bug.cgi?id=1904971 .

Comment 42 Giulio Fidente 2021-01-20 10:41:35 UTC
*** Bug 1904971 has been marked as a duplicate of this bug. ***

Comment 58 errata-xmlrpc 2021-09-15 07:07:46 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 (Red Hat OpenStack Platform (RHOSP) 16.2 enhancement advisory), 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/RHEA-2021:3483


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