Description of problem: From [1] Nova Metadata API service Starting from the Stein release, the Nova Metadata API service can be run either globally or per cell using the api.local_metadata_per_cell configuration option. Global If you have networks that span cells, you might need to run Nova metadata API globally. When running globally, it should be configured as an API-level service with access to the api_database.connection information. The nova metadata API service must not be run as a standalone service in this case (e.g. must not be run via the nova-api-metadata script). Local per cell Running Nova metadata API per cell can have better performance and data isolation in a muli-cell deployment. If your networks are segmented along cell boundaries, then you can run Nova metadata API service per cell. If you choose to run it per cell, you should also configure each Neutron metadata-agent to point to the corresponding nova-metadata-api. The nova metadata API service must be run as a standalone service in this case (e.g. must be run via the nova-api-metadata script). [1] https://docs.openstack.org/nova/latest/user/cellsv2-layout.html#nova-metadata-api-service Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
*** Bug 1767418 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2020:0283