Devstack deployment on Jammy Ubuntu fails

[Arkady Shtempler]

I'm trying to install Devstack using: https://cloud-images.ubuntu.com/daily/server/jammy/current/ (which is listed in supported distros: https://opendev.org/openstack/devstack/src/branch/master/stack.sh#L233-L235) and it fails to be deployed, the first issue I've seen was: No module named 'django:

### Django is missing ###
"d /var/run/uwsgi 0755 stack root", "/etc/tmpfiles.d/uwsgi.conf:1: Line references path below legacy directory /var/run/, updating /var/run/uwsgi → /run/uwsgi; please update the tmpfiles.d/ drop-in file accordingly.", "ProxyPass \"/dns\" \"unix:/var/run/uwsgi/designate-api-wsgi.socket|uwsgi://uwsgi-uds-designate-api-wsgi\" retry=0 acquire=1 ", "Enabling site designate-api-wsgi.", "To activate the new configuration, you need to run:", " systemctl reload apache2", "proxy (enabled by site administrator)", "proxy_http (enabled by site administrator)", "ProxyPass \"/dns\" \"http://127.0.0.1:60053\" retry=0", "Traceback (most recent call last):", " File \"/opt/stack/designate-dashboard/designatedashboard/../manage.py\", line 22, in <module>", " from django.core.management import execute_from_command_line # noqa", "ModuleNotFoundError: No module named 'django'", "exit_trap: cleaning up child processes", "Error on exit"]}

the additional attempt executing ./stack.sh fails on keystone with:
### keystone did not start ###
+functions-common:_run_under_systemd:1633 sudo systemctl enable <email address hidden>
+functions-common:_run_under_systemd:1634 sudo systemctl start <email address hidden>
+functions-common:run_process:1666 time_stop run_process
+functions-common:time_stop:2400 local name
+functions-common:time_stop:2401 local end_time
+functions-common:time_stop:2402 local elapsed_time
+functions-common:time_stop:2403 local total
+functions-common:time_stop:2404 local start_time
+functions-common:time_stop:2406 name=run_process
+functions-common:time_stop:2407 start_time=1695027500485
+functions-common:time_stop:2409 [[ -z 1695027500485 ]]
++functions-common:time_stop:2412 date +%s%3N
+functions-common:time_stop:2412 end_time=1695027501902
+functions-common:time_stop:2413 elapsed_time=1417
+functions-common:time_stop:2414 total=405
+functions-common:time_stop:2416 _TIME_START[$name]=
+functions-common:time_stop:2417 _TIME_TOTAL[$name]=1822
+lib/keystone:start_keystone:569 echo 'Waiting for keystone to start...'
Waiting for keystone to start...
+lib/keystone:start_keystone:575 local service_uri=http://192.168.122.80/identity/v3/
+lib/keystone:start_keystone:577 wait_for_service 60 http://192.168.122.80/identity/v3/
+functions:wait_for_service:457 local timeout=60
+functions:wait_for_service:458 local url=http://192.168.122.80/identity/v3/
+functions:wait_for_service:459 local rval=0
+functions:wait_for_service:460 time_start wait_for_service
+functions-common:time_start:2386 local name=wait_for_service
+functions-common:time_start:2387 local start_time=
+functions-common:time_start:2388 [[ -n '' ]]
++functions-common:time_start:2391 date +%s%3N
+functions-common:time_start:2391 _TIME_START[$name]=1695027502030
+functions:wait_for_service:461 timeout 60 bash -x
++:: curl -g -k --noproxy '*' -s -o /dev/null -w '%{http_code}' http://192.168.122.80/identity/v3/
+functions:wait_for_service:461 rval=124
+functions:wait_for_service:466 time_stop wait_for_service
+functions-common:time_stop:2400 local name
+functions-common:time_stop:2401 local end_time
+functions-common:time_stop:2402 local elapsed_time
+functions-common:time_stop:2403 local total
+functions-common:time_stop:2404 local start_time
+functions-common:time_stop:2406 name=wait_for_service
+functions-common:time_stop:2407 start_time=1695027502030
+functions-common:time_stop:2409 [[ -z 1695027502030 ]]
++functions-common:time_stop:2412 date +%s%3N
+functions-common:time_stop:2412 end_time=1695027562160
+functions-common:time_stop:2413 elapsed_time=60130
+functions-common:time_stop:2414 total=0
+functions-common:time_stop:2416 _TIME_START[$name]=
+functions-common:time_stop:2417 _TIME_TOTAL[$name]=60130
+functions:wait_for_service:467 return 124
+lib/keystone:start_keystone:578 die 578 'keystone did not start'
+functions-common:die:264 local exitcode=0
[Call Trace]
./stack.sh:1134:start_keystone
/opt/stack/devstack/lib/keystone:578:die
[ERROR] /opt/stack/devstack/lib/keystone:578 keystone did not start
exit_trap: cleaning up child processes
Error on exit

I've also tried using previous Jammy buiids and result was the same.

Notes:
1) Used image:https://cloud-images.ubuntu.com/daily/server/jammy/current/jammy-server-cloudimg-amd64.img
2) Localrc configuration file: https://github.com/itzikb/ansible-devstack/blob/master/roles/devstack/templates/designate.conf

[Arkady Shtempler (ashtempl)]

The issue seems to be related to Horizon.
I was able to deploy Devstack after remarking this line:
ENABLED_SERVICES+=,horizon
in local.conf

[Martin Kopec (mkopec)]

Interesting, I deleted every mention of designate from your local.conf and it deployed successfully.

At some point I got the following error from designate:
/opt/stack/designate/devstack/designate_plugins/backend-bind9: line 40: is_suse: command not found

That made me think that designate uses/depends on old code (is_suse doesn't exist in devstack anymore), therefore I tried to run it without designate service which surprisingly worked.

I think that the root cause will be somewhere in 'old code' which might be included accidentally. The local.conf you shared may contain old extensions that include the 'old code'. That's something frickler raised as well during our last office hour:
https://meetings.opendev.org/meetings/qa/2023/qa.2023-09-19-15.00.log.html#l-116

[Dr. Jens Harbott (j-harbott)]

If the deployment with the designate plugin fails, it is a bug in designate, not in devstack

[Michael Johnson (johnsom)]

Closing this as resolved in this patch:
https://github.com/openstack/designate/commit/efaeb9085ea7fa0e3a22d31d5c9add4d903532b3