openstack/kolla.git/docker/nova/nova-api/extend_start.sh, branch stable/2026.1

Remove httpd_setup calls from api containers

2026-04-28T11:22:25+00:00

We have dropped mod_wsgi support from services in [1]. [1]: https://review.opendev.org/c/openstack/kolla-ansible/+/982414 Change-Id: Ie5da8427706dfb74bad4e174c990355a6870114c Signed-off-by: Michal Nasiadka

Sync only local cell in nova bootstrap & upgrade

2023-12-21T09:46:59+00:00

Added the --local_cell argument to nova db sync commands during bootstrap and upgrade. This was previously thought to have no effect [1], but has since been discovered to fail when rotating the nova database password. [1] https://opendev.org/openstack/kolla-ansible/src/branch/master/ansible/roles/nova/tasks/bootstrap_service.yml#L2-L3 Closes-Bug: #2045558 Change-Id: Ic64eb51325b3503a14ebab9b9ff2f4d9caec734a

Add support for running Nova upgrade checks

2023-03-28T07:03:20+00:00

Related-Bug: #1957080 Change-Id: I6cbbdfcd40a8f486a3a636b41d704ee6ffafb812

Refactor Apache httpd setup

2019-12-11T11:38:46+00:00

All Apache httpd setup has been moved to a new helper script, kolla_httpd_setup. This includes the existing clean of /run/httpd, /var/run/httpd, /tmp/httpd etc. Horizon has an additional bit of Apache config for Debian/binary, which has been kept in extend_start.sh for horizon. Change-Id: Ia2af74b69c151db0bd7e452460b0babcee50b282 Related: blueprint centos-rhel-8

Support DB bootstrap from Nova Conductor container

2019-08-20T16:22:40+00:00

Currently the Nova API container does all the database bootstrapping for Nova. In a deployment with more than one active cell, it makes more sense for the conductors to bootstrap their own databases, rather than have the Nova API container do it. This change adds support for that. Until the support is actually used, we leave Nova API as-is. Partially Implements: blueprint support-nova-cells Change-Id: Id3a78b6838a3aae04f5dd5bd6ec928359297cfd3

Run nova api_db sync before db sync

2019-06-17T10:07:01+00:00

Backport: Stein, Rocky Since cells v2 was introduced, nova operators must run two commands to migrate the database schemas of nova's databases - nova-manage api_db sync and nova-manage db sync. It is necessary to run them in this order, since the db sync may depend on schema changes made to the api database in the api_db sync. Executing the db sync first may fail, for example with the following seen in a Queens to Rocky upgrade: nova-manage db sync ERROR: Could not access cell0. Has the nova_api database been created? Has the nova_cell0 database been created? Has "nova-manage api_db sync" been run? Has "nova-manage cell_v2 map_cell0" been run? Is [api_database]/connection set in nova.conf? Is the cell0 database connection URL correct? Error: (pymysql.err.InternalError) (1054, u"Unknown column 'cell_mappings.disabled' in 'field list'") [SQL: u'SELECT cell_mappings.created_at AS cell_mappings_created_at, cell_mappings.updated_at AS cell_mappings_updated_at, cell_mappings.id AS cell_mappings_id, cell_mappings.uuid AS cell_mappings_uuid, cell_mappings.name 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 \nFROM cell_mappings \nWHERE cell_mappings.uuid = %(uuid_1)s \n LIMIT %(param_1)s'] [parameters: {u'uuid_1': '00000000-0000-0000-0000-000000000000', u'param_1': 1}] (Background on this error at: http://sqlalche.me/e/2j85) Despite this error, the command actually exits zero, so kolla does not notice the failure. This change reorders these two commands to run the api_db sync before the db sync. Change-Id: I0514c02aaee1a413a7979c3a426e0484df839861 Closes-Bug: #1832860

create missing apache2 directory on Debian/Ubuntu

2019-06-03T13:11:24+00:00

Ubuntu/source deployment of several images (horizon, placement-api, zun) failed with: + exec /usr/sbin/apache2 -DFOREGROUND apache2: Syntax error on line 80 of /etc/apache2/apache2.conf: DefaultRuntimeDir must be a valid directory, absolute or relative to ServerRoot Change-Id: Ie2a1077f7def0743f1403341985e2109aa490026

Fix nova-api extend_start.sh

2018-06-11T06:59:52+00:00

Patch https://review.openstack.org/#/c/558765 added an extra closure bracket }, this patch fixes it. Change-Id: I379ff17856509c9321b86c13a72eacc18f5c1202 Closes-Bug: #1775698

Apply Nova rolling upgrade logic

2018-06-05T09:54:37+00:00

This patchset apply Nova rolling upgrade logic [1] [1] https://docs.openstack.org/nova/latest/user/upgrade.html Change-Id: I2cc973896d08988c0db121673d357fd1d37e6e6c Implements: blueprint apply-service-upgrade-procedure

Fix if $user is root at extend_start

2017-05-12T12:40:52+00:00

In ubuntu is not evaluating correctly if $user == root check at extend_start. Changing to "$(whoami)" == 'root' fixes the issue Change-Id: I296a1f98764cdfa09650c483bc7beba53e6bdba4 Closes-Bug: #1690360