Compute Component: Error: (pymysql.err.ProgrammingError) (1146, "Table 'nova_api.cell_mappings' doesn't exist")

Bug #1940555 reported by wes hayutin
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
sean mooney
Fix Released

Bug Description

Is [api_database]/connection set in nova.conf?
Is the cell0 database connection URL correct?
Error: (pymysql.err.ProgrammingError) (1146, "Table 'nova_api.cell_mappings' doesn't exist")
[SQL: SELECT cell_mappings.created_at AS cell_mappings_created_at, cell_mappings.updated_at AS cell_mappings_updated_at, AS cell_mappings_id, cell_mappings.uuid AS cell_mappings_uuid, AS cell_mappings_name, cell_mappings.transport_url AS cell_mappings_transport_url, cell_mappings.database_connection AS cell_mappings_database_connection, cell_mappings.disabled AS cell_mappings_disabled
FROM cell_mappings
WHERE cell_mappings.uuid = %(uuid_1)s
 LIMIT %(param_1)s]
[parameters: {'uuid_1': '00000000-0000-0000-0000-000000000000', 'param_1': 1}]
(Background on this error at:

+ echo 'Running command: '\''/usr/bin/bootstrap_host_exec nova_conductor su nova -s /bin/bash -c '\''/usr/bin/nova-manage db sync '\'''\'''
+ exec /usr/bin/bootstrap_host_exec nova_conductor su nova -s /bin/bash -c ''\''/usr/bin/nova-manage' db sync \'
2021-08-19 08:17:33.982762 | fa163e06-c6d2-5dfd-0459-00000000197e | FATAL | Create containers managed by Podman for /var/lib/tripleo-config/container-startup-config/step_3 | standalone | error={"changed": false, "msg": "Failed containers: nova_api_db_sync, nova_api_map_cell0, nova_api_ensure_default_cell, nova_db_sync"}
2021-08-19 08:17:33.983320 | fa163e06-c6d2-5dfd-0459-00000000197e | TIMING | tripleo_container_manage : Create containers managed by Podman for /var/lib/tripleo-config/container-startup-config/step_3 | standalone | 0:19:23.159835 | 41.20s

Revision history for this message
wes hayutin (weshayutin) wrote :
Revision history for this message
melanie witt (melwitt) wrote :

Here's an error that was raised during the sync of the nova_api database [1]:

Running command: '/usr/bin/bootstrap_host_exec nova_api su nova -s /bin/bash -c '/usr/bin/nova-manage api_db sync''
+ echo 'Running command: '\''/usr/bin/bootstrap_host_exec nova_api su nova -s /bin/bash -c '\''/usr/bin/nova-manage api_db sync'\'''\'''
+ exec /usr/bin/bootstrap_host_exec nova_api su nova -s /bin/bash -c ''\''/usr/bin/nova-manage' api_db 'sync'\'''
An error has occurred:
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/nova/cmd/", line 2845, in main
    ret = fn(*fn_args, **fn_kwargs)
  File "/usr/lib/python3.6/site-packages/nova/cmd/", line 584, in sync
    return migration.db_sync(version, database='api')
  File "/usr/lib/python3.6/site-packages/nova/db/", line 144, in db_sync
    config.set_main_option('sqlalchemy.url', str(engine.url))
  File "/usr/lib/python3.6/site-packages/alembic/", line 243, in set_main_option
    self.set_section_option(self.config_ini_section, name, value)
  File "/usr/lib/python3.6/site-packages/alembic/", line 270, in set_section_option
    self.file_config.set(section, name, value)
  File "/usr/lib64/python3.6/", line 1193, in set
    super().set(section, option, value)
  File "/usr/lib64/python3.6/", line 894, in set
  File "/usr/lib64/python3.6/", line 402, in before_set
    "position %d" % (value, tmp_value.find('%')))
ValueError: invalid interpolation syntax in 'mysql+pymysql://nova_api:Jl6ip4yYTetmtrYWydWwJAcmI@' at position 91

Which would result in failure to create the nova_api database tables.


Changed in nova:
status: New → Triaged
importance: Undecided → Critical
assignee: nobody → sean mooney (sean-k-mooney)
Revision history for this message
sean mooney (sean-k-mooney) wrote :

this looks like a bug in nova which we think will resolve.
i have added nova to the bug and asigned it to me for now. stephen has already submitted ^ but ill work with them on it.

tl;dr we recently converted form sql alchamey migrate to alembic

as part fo that we have to override part of alembic default config and we intoduced a cast form

sqlalchemy.engine.url.URL to string

i believe that cast results in the / in being url encoded causing the error you are seeign in ooo

we dont see this in devstack since we dont set the read_defaut_file as far as i know in our jobs.

Changed in nova:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Submitter: "Zuul (22348)"
Branch: master

commit 6c5dd864c24bc8cec89dccbff68b63c3bc23ef70
Author: Stephen Finucane <email address hidden>
Date: Mon Aug 23 17:42:08 2021 +0100

    db: Handle parameters in DB strings

    As part of 'nova.db.migration', it is necessary to override the
    'sqlalchemy.url' config option used by alembic. We were doing this but
    we weren't handling the fact that we could receive encoded URL strings.
    This causes issues for the ConfigParser instead used under the hood, as
    noted in the alembic docs [1]:

      value – the value. Note that this value is passed to ConfigParser.set,
      which supports variable interpolation using pyformat (e.g.
      %(some_value)s). A raw percent sign not part of an interpolation
      symbol must therefore be escaped, e.g. %%. The given value may refer
      to another value already in the file using the interpolation format.

    Resolve the issue by escaping % with %%. The engine.url is always
    encoded therefore this can be done unconditionally.


    Closes-Bug: #1940555
    Change-Id: I74de55107a80af13df348f2bce49415b08028746
    Signed-off-by: Stephen Finucane <email address hidden>
    Co-Authored-By: Sean Mooney <email address hidden>

Changed in nova:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/nova

This issue was fixed in the openstack/nova release candidate.

Revision history for this message
Ronelle Landy (rlandy) wrote :

no trace in skiplist - closing out the tripleo branch

Changed in tripleo:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers