yahoo-eng-team team mailing list archive

[OpenStack Infra <1649341@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/409876
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=6764ff0db2aaa4dda0d804c7db886d3b64226674
Submitter: Jenkins
Branch:    master

commit 6764ff0db2aaa4dda0d804c7db886d3b64226674
Author: Matt Riedemann <mriedem@xxxxxxxxxx>
Date:   Mon Dec 12 12:52:27 2016 -0500

    Fix instructions for running simple_cell_setup
    
    Change ff6b9998bb977421a5cbc94878ced8542d910c9e enforces in
    a database migration that you've run the simple_cell_setup
    command for cells v2 but the instructions in the error and
    in the release note said to use 'nova-manage db' when it should
    be 'nova-manage cell_v2'.
    
    Change-Id: I8e71d1c7022d1000f26b7c16ed1c56f6e87ab8ac
    Closes-Bug: #1649341


** Changed in: 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:
  New
Status in tripleo:
  Triaged

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