yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #59969
[Bug 1649341] Re: Undercloud upgrade fails with "Cell mappings are not created, but required for Ocata"
Reviewed: https://review.openstack.org/409948
Committed: https://git.openstack.org/cgit/openstack/puppet-nova/commit/?id=4234ce3df430f16d3e9278e587238148db8e3a47
Submitter: Jenkins
Branch: master
commit 4234ce3df430f16d3e9278e587238148db8e3a47
Author: Alex Schultz <aschultz@xxxxxxxxxx>
Date: Mon Dec 12 14:52:57 2016 -0700
Add cell_v2 simple_cell_setup
As part of Ocata, nova has made the cell_v2 setup manditory for the
nova-api db sync process. This change adds a simple cell_v2 setup with a
cell0 and an execution of the 'nova-manage cell_v2 simple_cell_setup' as
part of the nova-api db setup and sync process.
Change-Id: Idfc369e9e17f7d5a30ce4ff52beb604dd4a6ac23
Closes-Bug: #1649341
** Changed in: puppet-nova
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1649341
Title:
Undercloud upgrade fails with "Cell mappings are not created, but
required for Ocata"
Status in OpenStack Compute (nova):
Fix Released
Status in puppet-nova:
Fix Released
Status in tripleo:
In Progress
Bug description:
Trying to upgrade with recent trunk nova and puppet-nova gives this
error:
Notice: /Stage[main]/Nova::Db::Sync_api/Exec[nova-db-sync-api]/returns: error: Cell mappings are not created, but required for Ocata. Please run nova-manage db simple_cell_setup before continuing.
Error: /usr/bin/nova-manage api_db sync returned 1 instead of one of [0]
Error: /Stage[main]/Nova::Db::Sync_api/Exec[nova-db-sync-api]/returns: change from notrun to 0 failed: /usr/bin/nova-manage api_db sync returned 1 instead of one of [0]
Debugging manually gives:
$ sudo /usr/bin/nova-manage api_db sync
error: Cell mappings are not created, but required for Ocata. Please run nova-manage db simple_cell_setup before continuing.
but...
$ sudo nova-manage db simple_cell_setup
usage: nova-manage db [-h]
{archive_deleted_rows,null_instance_uuid_scan,online_data_migrations,sync,version}
...
nova-manage db: error: argument action: invalid choice: 'simple_cell_setup' (choose from 'archive_deleted_rows', 'null_instance_uuid_scan', 'online_data_migrations', 'sync', 'version')
I tried adding openstack-nova* to the delorean-current whitelist, but with the latest nova packages there still appears to be this mismatch.
[stack@instack /]$ rpm -qa | grep nova
openstack-nova-conductor-15.0.0-0.20161212155146.909410c.el7.centos.noarch
python-nova-15.0.0-0.20161212155146.909410c.el7.centos.noarch
openstack-nova-scheduler-15.0.0-0.20161212155146.909410c.el7.centos.noarch
puppet-nova-10.0.0-0.20161211003757.09b9f7b.el7.centos.noarch
python2-novaclient-6.0.0-0.20161003181629.25117fa.el7.centos.noarch
openstack-nova-api-15.0.0-0.20161212155146.909410c.el7.centos.noarch
openstack-nova-cert-15.0.0-0.20161212155146.909410c.el7.centos.noarch
openstack-nova-common-15.0.0-0.20161212155146.909410c.el7.centos.noarch
openstack-nova-compute-15.0.0-0.20161212155146.909410c.el7.centos.noarch
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1649341/+subscriptions