Reviewed: https://review.openstack.org/419121
Committed:
https://git.openstack.org/cgit/openstack/instack-undercloud/commit/?id=ad47a3c40fbf13427457e4b0b9fb7a684de6377a
Submitter: Jenkins
Branch: master
commit ad47a3c40fbf13427457e4b0b9fb7a684de6377a
Author: Alex Schultz <aschu...@redhat.com>
Date: Wed Jan 11 13:18:55 2017 -0700
Run cell v2 setup differently for upgrades
For the upgrades from Newton, we need to run the cell v2 simple setup
before running the api db sync since we did not deploy cell v2 in
Newton. Starting with Ocata, api db sync errors if the cell v2 simple
setup has not been done.
Change-Id: I80ecc0943e08952fbc29c55da9d4ba8f51b0eb7e
Closes-Bug: #1649341
** Changed in: tripleo
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 OpenStack Compute (nova) newton series:
In Progress
Status in puppet-nova:
Fix Released
Status in tripleo:
Fix Released
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
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
