Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1625166

Summary: During osp9 to 10 upgrade,one get "aborted: /lib64/librbd.so.1: undefined symbol" when spawning a vm.
Product: Red Hat OpenStack Reporter: Sofer Athlan-Guyot <sathlang>
Component: openstack-tripleo-heat-templatesAssignee: Sofer Athlan-Guyot <sathlang>
Status: CLOSED CURRENTRELEASE QA Contact: Yurii Prokulevych <yprokule>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 10.0 (Newton)CC: augol, gfidente, jamsmith, jdillama, jdurgin, mburns, sathlang, yprokule
Target Milestone: z10Keywords: Regression, Triaged, ZStream
Target Release: 10.0 (Newton)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-5.3.10-20.el7ost Doc Type: Bug Fix
Doc Text:
This update fixes an OSP 9 to OSP 10 upgrade issue that sometimes prevented the spawning of VMs during upgrades. Prior to this update, VMs could not be spawned between ceph/compute upgrade and convergence, because ceph librados libraries were open in memory, conflicting with the upgraded client on disk. That triggered calls to non-existent (in-memory) symbols. To work around this issue, nova-compute is restarted on compute nodes to synchronize the disk and the in-memory client libraries.
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-10 09:41:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Sofer Athlan-Guyot 2018-09-04 09:58:27 UTC
Description of problem:  Doing a osp9/10 upgrade, before convergence and after ceph/compute upgarde one cannot spawn vm with ceph backend and get:

Build of instance cc5b7484-e201-496c-af5b-75297a7f8870 aborted: /lib64/librbd.so.1: undefined symbol: _ZN8librados5Rados15aio_watch_flushEPNS_13AioCompletionE', u'code': 500, u'details': u'  File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 1787, 

This is very similar to https://bugzilla.redhat.com/show_bug.cgi?id=1273194#c4 

Restarting nova-compute on all the compute nodes "fixed" the issue.

Creating a workaround in tht will be easy enough, but I'll re-open 1273194 to notify people about its existence.

librbd1-10.2.10-28.el7cp.x86_64
openstack-nova-compute-14.1.0-26.el7ost.noarch