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

Bug 1250599

Summary: openstack-nova requires python-oslo-serialization
Product: Red Hat OpenStack Reporter: Lars Kellogg-Stedman <lars>
Component: openstack-novaAssignee: Eoghan Glynn <eglynn>
Status: CLOSED DUPLICATE QA Contact: nlevinki <nlevinki>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0 (Kilo)CC: berrange, dasmith, eglynn, kchamart, ndipanov, pbrady, sbauza, sferdjao, sgordon, vromanso, yeylon
Target Milestone: ---   
Target Release: 8.0 (Liberty)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-09-28 16:23:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1249564, 1266956    

Description Lars Kellogg-Stedman 2015-08-05 14:18:42 UTC 
openstack-nova in OSP 7 requires python-oslo-serialization.  After upgrading from OSP 6, running nova-manage db sync fails with:

stderr: Traceback (most recent call last):
  File "/usr/bin/nova-manage", line 6, in <module>
    from nova.cmd.manage import main
  File "/usr/lib/python2.7/site-packages/nova/cmd/manage.py", line 65, in <module>
    from oslo_log import log as logging
  File "/usr/lib/python2.7/site-packages/oslo_log/log.py", line 47, in <module>
    from oslo_log import formatters
  File "/usr/lib/python2.7/site-packages/oslo_log/formatters.py", line 24, in <module>
    from oslo_serialization import jsonutils
ImportError: No module named oslo_serialization
Can't determine the existing sync level.
Please ensure the database is running and already initialised.

In version:

openstack-nova-common-2015.1.0-16.el7ost.noarch
Comment 3 Lars Kellogg-Stedman 2015-09-28 16:23:50 UTC 
Rolled into #1266956

*** This bug has been marked as a duplicate of bug 1266956 ***