[Kolla-ansible][epoxy]nova problems at restart
Hello everyone, I need your help. II will try to explain my problem by providing a lot of information. I have been trying to solve it for 3 days, without success. In May, my old cluster became too small for the 200 students using it, so I started installing a new cluster. Six nodes, three in one data center, three in another. After testing with Bobcat and Caracal (unsatisfactory, with numerous issues, especially with authentication and display in Horizon), I tried Epoxy. I installed everything I needed and tested it. It was a real success. It was very fast in its new configuration, and I thought everything would be ready by September. In May, my old cluster was becoming too small for the 200 students using it, so I started installing a new cluster. 6 nodes, 3 in one data center, 3 in another. After testing with Bobcat and Caracal (unsatisfactory, with numerous issues, especially with authentication and display in Horizon), I tried Epoxy. I installed everything I needed and tested it. It was a real success. It was very fast in its new configuration; I thought everything would be ready by September. At the beginning of July, I was told to shut down everything, due to electrical maintenance in a data center. I shut everything down. 3 days later, I restarted it, and nothing worked anymore. However, it was simply a shutdown/restart of the servers. The problems are with Nova. Here's some information and logs, if you can help me restart the cluster. So Epoxy on Ubuntu 2404. (venv2) user1@ordi1:~/OPENSTACK/INSTALL$ kolla-ansible --version kolla-ansible 20.0.1.dev4 Since nova didn't want to work I did this: (venv2) user1@ordi1:~/OPENSTACK/INSTALL$ kolla-ansible reconfigure -I multinode -t nova ERROR with a task: TASK [nova-cell : Waiting for nova-compute services to register themselves] **************** skipping: [ordi2] skipping: [ordi3] skipping: [ordi4] skipping: [ordi5] skipping: [ordi6] An exception occurred during task execution. To see the full traceback, use -vvv. The error was: json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) fatal: [ordi1]: FAILED! => {"msg": "Unexpected failure during module execution: Expecting value: line 1 column 1 (char 0)", "stdout": ""} I search with Google and find this (BUG2 in the link): https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.... But I am in 20.0.1.dev4 There is a lot of logs (with nova)….. total 533340 -rw-r--r-- 1 42436 42436 0 juil. 17 06:42 nova-api.log -rw-r--r-- 1 42436 42436 105512247 juil. 17 06:42 nova-api.log.1 -rw-r--r-- 1 42436 42436 2460643 juil. 6 06:40 nova-api.log.2.gz -rw-r--r-- 1 42436 42436 7305818 juil. 5 06:31 nova-api.log.3.gz -rw-r--r-- 1 42436 42436 7234505 juil. 2 06:48 nova-api.log.4.gz -rw-r--r-- 1 42436 42436 2356307 juin 29 06:35 nova-api.log.5.gz -rw-r--r-- 1 42436 42436 7181854 juin 28 06:49 nova-api.log.6.gz -rw-r--r-- 1 42436 42436 56065234 juil. 18 09:06 nova-api-uwsgi.log -rw-r--r-- 1 42436 42436 113689390 juil. 17 06:42 nova-api-uwsgi.log.1 -rw-r--r-- 1 42436 42436 2150056 juil. 6 06:40 nova-api-uwsgi.log.2.gz -rw-r--r-- 1 42436 42436 6393602 juil. 5 06:31 nova-api-uwsgi.log.3.gz -rw-r--r-- 1 42436 42436 6383183 juil. 2 06:48 nova-api-uwsgi.log.4.gz -rw-r--r-- 1 42436 42436 2083376 juin 29 06:35 nova-api-uwsgi.log.5.gz -rw-r--r-- 1 42436 42436 6351824 juin 28 06:49 nova-api-uwsgi.log.6.gz -rw-r--r-- 1 42436 42436 1467596 juil. 18 09:06 nova-compute.log -rw-r--r-- 1 42436 42436 2626598 juil. 18 09:06 nova-conductor.log -rw-r--r-- 1 42436 42436 44883046 juil. 18 06:45 nova-conductor.log.1 -rw-r--r-- 1 42436 42436 7154 juil. 18 08:58 nova-manage.log -rw-r--r-- 1 42436 42436 221050 juil. 16 15:08 nova-metadata.log -rw-r--r-- 1 42436 42436 28094556 juil. 18 09:06 nova-metadata-uwsgi.log -rw-r--r-- 1 42436 42436 74174166 juil. 17 06:42 nova-metadata-uwsgi.log.1 -rw-r--r-- 1 42436 42436 5650339 juil. 5 06:31 nova-metadata-uwsgi.log.2.gz -rw-r--r-- 1 42436 42436 1861983 juin 29 06:35 nova-metadata-uwsgi.log.3.gz -rw-r--r-- 1 42436 42436 5601477 juin 27 06:53 nova-metadata-uwsgi.log.4.gz -rw-r--r-- 1 42436 42436 5640648 juin 21 06:36 nova-metadata-uwsgi.log.5.gz -rw-r--r-- 1 42436 42436 1871248 juin 15 06:43 nova-metadata-uwsgi.log.6.gz -rw-r--r-- 1 42436 42436 111880 juil. 16 15:08 nova-novncproxy.log -rw-r--r-- 1 42436 42436 2668833 juil. 18 09:06 nova-scheduler.log -rw-r--r-- 1 42436 42436 45997165 juil. 18 06:45 nova-scheduler.log.1 -rw-r--r-- 1 42436 42436 0 mai 15 08:47 privsep-helper.log 2 containers have problems: docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 6231ee0f3c97 quay.io/openstack.kolla/nova-scheduler:2025.1-ubuntu-noble "dumb-init --single-…" 10 minutes ago Exited (1) 5 seconds ago nova_scheduler 57707a9d136e quay.io/openstack.kolla/nova-conductor:2025.1-ubuntu-noble "dumb-init --single-…" 39 hours ago Exited (1) 4 seconds ago nova_conductor Have a look to nova_conductor.log (same thing with nova_scheduler): 2025-07-18 09:08:25.170 7 ERROR nova.scheduler.client.report [-] Failed to initialize placement client (is keystone available?): openstack.exceptions.NotSupported: The placement service for 192.168.100.100:RegionOne exists but does not have any supported versions. 2025-07-18 09:08:25.171 7 ERROR nova.conductor.manager [-] Fatal error initializing placement client: The placement service for 192.168.100.100:RegionOne exists but does not have any supported versions.: openstack.exceptions.NotSupported: The placement service for 192.168.100.100:RegionOne exists but does not have any supported versions. 2025-07-18 09:08:25.172 7 CRITICAL nova [-] Unhandled error: openstack.exceptions.NotSupported: The placement service for 192.168.100.100:RegionOne exists but does not have any supported versions. 2025-07-18 09:08:25.172 7 ERROR nova Traceback (most recent call last): 2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/bin/nova-conductor", line 8, in <module> 2025-07-18 09:08:25.172 7 ERROR nova sys.exit(main()) 2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^ 2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/cmd/conductor.py", line 45, in main 2025-07-18 09:08:25.172 7 ERROR nova server = service.Service.create(binary='nova-conductor', 2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/service.py", line 256, in create 2025-07-18 09:08:25.172 7 ERROR nova service_obj = cls(host, binary, topic, manager, 2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/service.py", line 120, in __init__ 2025-07-18 09:08:25.172 7 ERROR nova self.manager = manager_class(host=self.host, *args, **kwargs) 2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/conductor/manager.py", line 124, in __init__ 2025-07-18 09:08:25.172 7 ERROR nova self.compute_task_mgr = ComputeTaskManager() 2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^^^^^^^^^^^^^^^ 2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/conductor/manager.py", line 255, in __init__ 2025-07-18 09:08:25.172 7 ERROR nova self.report_client 2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/conductor/manager.py", line 283, in report_client 2025-07-18 09:08:25.172 7 ERROR nova return report.report_client_singleton() 2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/scheduler/client/report.py", line 91, in report_client_singleton 2025-07-18 09:08:25.172 7 ERROR nova PLACEMENTCLIENT = SchedulerReportClient() 2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^^^^^^^^^^^^^^^^^^ 2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/scheduler/client/report.py", line 237, in __init__ 2025-07-18 09:08:25.172 7 ERROR nova self._client = self._create_client() 2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^^^^^^^^^^^^^^^^ 2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/scheduler/client/report.py", line 280, in _create_client 2025-07-18 09:08:25.172 7 ERROR nova client = self._adapter or utils.get_sdk_adapter( 2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^^^^^^^^^^^^^^^^^ 2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/utils.py", line 1035, in get_sdk_adapter 2025-07-18 09:08:25.172 7 ERROR nova return getattr(conn, service_type.replace('-', '_')) 2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/openstack/service_description.py", line 88, in __get__ 2025-07-18 09:08:25.172 7 ERROR nova proxy = self._make_proxy(instance) 2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/openstack/service_description.py", line 290, in _make_proxy 2025-07-18 09:08:25.172 7 ERROR nova raise exceptions.NotSupported( 2025-07-18 09:08:25.172 7 ERROR nova openstack.exceptions.NotSupported: The placement service for 192.168.100.100:RegionOne exists but does not have any supported versions. 2025-07-18 09:08:25.172 7 ERROR nova Another thing is strange: Autre point bizarre: tail -f /var/log/kolla/placement/placement-api-uwsgi.log --- no python application found, check your startup logs for errors --- [pid: 1092|app: -1|req: -1/307186] 192.168.100.4 () {22 vars in 215 bytes} [Fri Jul 18 09:11:28 2025] GET / => generated 21 bytes in 0 msecs (HTTP/1.0 500) 3 headers in 102 bytes (0 switches on core 0) What can I do ? Can you help me to find a solution to restart my Openstack ? Thanks a lot if you can. Franck
so just a suggestion i would basiclly try turning it off and on a agin. so i think the problem is that you limit the reconfig to nova but the srrro seam to indicate they placement is not runing or it not a new enough verions. so in epoxy i belive kolla has a stop command so i woudl be tempted to do a stop, pull the latest version of the kolla images with the pull action and then do anohter deploy rather then reconfigure. recornigure at least in the past is actully just ment to update the config file and restart the contiers in place. deploy does that but it can also update to newever version fo the images if you pull them first. i have not worked on kolla in a very long time nad i rearly update my home deployment so the kolla team may have a better suggestion but that would be what i tired if it was my home cluster. note that when doing deploy i woudl allow it to run for all service his is effectivly jsut doing a mindor update to latest stable release of epoxy. i would also make sure your kolla-ansible is using the latest epoxy version too incase your are hitting a fix know issue. thre is now a 20.1.0 aviable. if your using it form git you can obviously just do a git pull but done forget to make sure you updated the deps pip3 install --upgrade 'ansible-core>=2.17,<2.18.99' kolla-ansible==20.1.0 kolla-ansible install-deps i think the root of your problem is with the fact palcement is not starting properly adn returnningn 500s the python application found error i think is because of setuptools 80 and the the way the wsig script used to be generate becore we added a pyrpoject.toml so im hoping using the latest images will have that resolved. my home clustier is still on caracal and i need to upgrade it soon but i cant confirm if that will solve the issue but it likely that it will. On 18/07/2025 08:27, Franck VEDEL (UGA) wrote:
Hello everyone, I need your help. II will try to explain my problem by providing a lot of information. I have been trying to solve it for 3 days, without success. In May, my old cluster became too small for the 200 students using it, so I started installing a new cluster. Six nodes, three in one data center, three in another. After testing with Bobcat and Caracal (unsatisfactory, with numerous issues, especially with authentication and display in Horizon), I tried Epoxy. I installed everything I needed and tested it. It was a real success. It was very fast in its new configuration, and I thought everything would be ready by September.
In May, my old cluster was becoming too small for the 200 students using it, so I started installing a new cluster. 6 nodes, 3 in one data center, 3 in another. After testing with Bobcat and Caracal (unsatisfactory, with numerous issues, especially with authentication and display in Horizon), I tried Epoxy. I installed everything I needed and tested it. It was a real success. It was very fast in its new configuration; I thought everything would be ready by September. At the beginning of July, I was told to shut down everything, due to electrical maintenance in a data center. I shut everything down. 3 days later, I restarted it, and nothing worked anymore. However, it was simply a shutdown/restart of the servers.
The problems are with Nova. Here's some information and logs, if you can help me restart the cluster.
So Epoxy on Ubuntu 2404.
(venv2) *user1@ordi1*:*~/OPENSTACK/INSTALL*$ kolla-ansible --version
kolla-ansible 20.0.1.dev4
Since nova didn't want to work I did this:
(venv2) *user1@ordi1*:*~/OPENSTACK/INSTALL*$ kolla-ansible reconfigure -I multinode -t nova
ERROR with a task:
TASK [nova-cell : Waiting for nova-compute services to register themselves] ****************
skipping: [ordi2]
skipping: [ordi3]
skipping: [ordi4]
skipping: [ordi5]
skipping: [ordi6]
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
fatal: [ordi1]: FAILED! => {"msg": "Unexpected failure during module execution: Expecting value: line 1 column 1 (char 0)", "stdout": ""}
I search with Google and find this (BUG2 in the link): https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack....
But I am in 20.0.1.dev4
There is a lot of logs (with nova)…..
total 533340
-rw-r--r-- 1 42436 42436 0 juil. 17 06:42 nova-api.log
-rw-r--r-- 1 42436 42436 105512247 juil. 17 06:42 nova-api.log.1
-rw-r--r-- 1 42436 42436 2460643 juil. 6 06:40 *nova-api.log.2.gz*
-rw-r--r-- 1 42436 42436 7305818 juil. 5 06:31 *nova-api.log.3.gz*
-rw-r--r-- 1 42436 42436 7234505 juil. 2 06:48 *nova-api.log.4.gz*
-rw-r--r-- 1 42436 42436 2356307 juin 29 06:35 *nova-api.log.5.gz*
-rw-r--r-- 1 42436 42436 7181854 juin 28 06:49 *nova-api.log.6.gz*
-rw-r--r-- 1 42436 42436 56065234 juil. 18 09:06 nova-api-uwsgi.log
-rw-r--r-- 1 42436 42436 113689390 juil. 17 06:42 nova-api-uwsgi.log.1
-rw-r--r-- 1 42436 42436 2150056 juil. 6 06:40 *nova-api-uwsgi.log.2.gz*
-rw-r--r-- 1 42436 42436 6393602 juil. 5 06:31 *nova-api-uwsgi.log.3.gz*
-rw-r--r-- 1 42436 42436 6383183 juil. 2 06:48 *nova-api-uwsgi.log.4.gz*
-rw-r--r-- 1 42436 42436 2083376 juin 29 06:35 *nova-api-uwsgi.log.5.gz*
-rw-r--r-- 1 42436 42436 6351824 juin 28 06:49 *nova-api-uwsgi.log.6.gz*
-rw-r--r-- 1 42436 42436 1467596 juil. 18 09:06 nova-compute.log
-rw-r--r-- 1 42436 42436 2626598 juil. 18 09:06 nova-conductor.log
-rw-r--r-- 1 42436 42436 44883046 juil. 18 06:45 nova-conductor.log.1
-rw-r--r-- 1 42436 42436 7154 juil. 18 08:58 nova-manage.log
-rw-r--r-- 1 42436 42436 221050 juil. 16 15:08 nova-metadata.log
-rw-r--r-- 1 42436 42436 28094556 juil. 18 09:06 nova-metadata-uwsgi.log
-rw-r--r-- 1 42436 42436 74174166 juil. 17 06:42 nova-metadata-uwsgi.log.1
-rw-r--r-- 1 42436 42436 5650339 juil. 5 06:31 *nova-metadata-uwsgi.log.2.gz*
-rw-r--r-- 1 42436 42436 1861983 juin 29 06:35 *nova-metadata-uwsgi.log.3.gz*
-rw-r--r-- 1 42436 42436 5601477 juin 27 06:53 *nova-metadata-uwsgi.log.4.gz*
-rw-r--r-- 1 42436 42436 5640648 juin 21 06:36 *nova-metadata-uwsgi.log.5.gz*
-rw-r--r-- 1 42436 42436 1871248 juin 15 06:43 *nova-metadata-uwsgi.log.6.gz*
-rw-r--r-- 1 42436 42436 111880 juil. 16 15:08 nova-novncproxy.log
-rw-r--r-- 1 42436 42436 2668833 juil. 18 09:06 nova-scheduler.log
-rw-r--r-- 1 42436 42436 45997165 juil. 18 06:45 nova-scheduler.log.1
-rw-r--r-- 1 42436 42436 0 mai 15 08:47 privsep-helper.log
2 containers have problems:
docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
6231ee0f3c97 quay.io/openstack.kolla/nova-scheduler:2025.1-ubuntu-noble "dumb-init --single-…" 10 minutes ago Exited (1) 5 seconds ago nova_scheduler
57707a9d136e quay.io/openstack.kolla/nova-conductor:2025.1-ubuntu-noble "dumb-init --single-…" 39 hours ago Exited (1) 4 seconds ago nova_conductor
Have a look to nova_conductor.log (same thing with nova_scheduler):
2025-07-18 09:08:25.170 7 ERROR nova.scheduler.client.report [-] Failed to initialize placement client (is keystone available?): openstack.exceptions.NotSupported: The placement service for 192.168.100.100:RegionOne exists but does not have any supported versions.
2025-07-18 09:08:25.171 7 ERROR nova.conductor.manager [-] Fatal error initializing placement client: The placement service for 192.168.100.100:RegionOne exists but does not have any supported versions.: openstack.exceptions.NotSupported: The placement service for 192.168.100.100:RegionOne exists but does not have any supported versions.
2025-07-18 09:08:25.172 7 CRITICAL nova [-] Unhandled error: openstack.exceptions.NotSupported: The placement service for 192.168.100.100:RegionOne exists but does not have any supported versions.
2025-07-18 09:08:25.172 7 ERROR nova Traceback (most recent call last):
2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/bin/nova-conductor", line 8, in <module>
2025-07-18 09:08:25.172 7 ERROR nova sys.exit(main())
2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^
2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/cmd/conductor.py", line 45, in main
2025-07-18 09:08:25.172 7 ERROR nova server = service.Service.create(binary='nova-conductor',
2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/service.py", line 256, in create
2025-07-18 09:08:25.172 7 ERROR nova service_obj = cls(host, binary, topic, manager,
2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/service.py", line 120, in __init__
2025-07-18 09:08:25.172 7 ERROR nova self.manager = manager_class(host=self.host, *args, **kwargs)
2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/conductor/manager.py", line 124, in __init__
2025-07-18 09:08:25.172 7 ERROR nova self.compute_task_mgr = ComputeTaskManager()
2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^^^^^^^^^^^^^^^
2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/conductor/manager.py", line 255, in __init__
2025-07-18 09:08:25.172 7 ERROR nova self.report_client
2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/conductor/manager.py", line 283, in report_client
2025-07-18 09:08:25.172 7 ERROR nova return report.report_client_singleton()
2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/scheduler/client/report.py", line 91, in report_client_singleton
2025-07-18 09:08:25.172 7 ERROR nova PLACEMENTCLIENT = SchedulerReportClient()
2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^^^^^^^^^^^^^^^^^^
2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/scheduler/client/report.py", line 237, in __init__
2025-07-18 09:08:25.172 7 ERROR nova self._client = self._create_client()
2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^^^^^^^^^^^^^^^^
2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/scheduler/client/report.py", line 280, in _create_client
2025-07-18 09:08:25.172 7 ERROR nova client = self._adapter or utils.get_sdk_adapter(
2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^^^^^^^^^^^^^^^^^
2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/utils.py", line 1035, in get_sdk_adapter
2025-07-18 09:08:25.172 7 ERROR nova return getattr(conn, service_type.replace('-', '_'))
2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/openstack/service_description.py", line 88, in __get__
2025-07-18 09:08:25.172 7 ERROR nova proxy = self._make_proxy(instance)
2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/openstack/service_description.py", line 290, in _make_proxy
2025-07-18 09:08:25.172 7 ERROR nova raise exceptions.NotSupported(
2025-07-18 09:08:25.172 7 ERROR nova openstack.exceptions.NotSupported: The placement service for 192.168.100.100:RegionOne exists but does not have any supported versions.
2025-07-18 09:08:25.172 7 ERROR nova
Another thing is strange:
Autre point bizarre:
tail -f /var/log/kolla/placement/placement-api-uwsgi.log
--- no python application found, check your startup logs for errors ---
[pid: 1092|app: -1|req: -1/307186] 192.168.100.4 () {22 vars in 215 bytes} [Fri Jul 18 09:11:28 2025] GET / => generated 21 bytes in 0 msecs (HTTP/1.0 500) 3 headers in 102 bytes (0 switches on core 0)
What can I do ? Can you help me to find a solution to restart my Openstack ? Thanks a lot if you can.
Franck
Thansk a lot for your help. I'm afraid of making a mistake... Are the different operations the following: kolla-ansible -i multinode stop pip3 install --upgrade 'ansible-core>=2.17,<2.18.99' kolla-ansible==20.1.0 kolla-ansible install-deps kolla-ansible -i multinode pull kolla-ansible -i multinode deploy Will I get the templates and images back? Franck
Le 18 juil. 2025 à 16:50, Sean Mooney <smooney@redhat.com> a écrit :
so just a suggestion
i would basiclly try turning it off and on a agin.
so i think the problem is that you limit the reconfig to nova but the srrro seam to indicate they placement is not runing or it not a new enough verions.
so in epoxy i belive kolla has a stop command
so i woudl be tempted to do a stop, pull the latest version of the kolla images with the pull action and then do anohter deploy rather then reconfigure.
recornigure at least in the past is actully just ment to update the config file and restart the contiers in place.
deploy does that but it can also update to newever version fo the images if you pull them first.
i have not worked on kolla in a very long time nad i rearly update my home deployment so the kolla team may have a better suggestion but
that would be what i tired if it was my home cluster.
note that when doing deploy i woudl allow it to run for all service his is effectivly jsut doing a mindor update to latest stable release of epoxy.
i would also make sure your kolla-ansible is using the latest epoxy version too incase your are hitting a fix know issue. thre is now a 20.1.0 aviable.
if your using it form git you can obviously just do a git pull but done forget to make sure you updated the deps
pip3 install --upgrade 'ansible-core>=2.17,<2.18.99' kolla-ansible==20.1.0 kolla-ansible install-deps
i think the root of your problem is with the fact palcement is not starting properly adn returnningn 500s
the python application found error i think is because of setuptools 80 and the the way the wsig script used to be generate becore we added a pyrpoject.toml
so im hoping using the latest images will have that resolved.
my home clustier is still on caracal and i need to upgrade it soon but i cant confirm if that will solve the issue but it likely that it will.
On 18/07/2025 16:20, Franck VEDEL (UGA) wrote:
Thansk a lot for your help.
I'm afraid of making a mistake...
Are the different operations the following:
kolla-ansible -i multinode stop pip3 install --upgrade 'ansible-core>=2.17,<2.18.99' kolla-ansible==20.1.0 kolla-ansible install-deps kolla-ansible -i multinode pull kolla-ansible -i multinode deploy
yes those are the steps i was suggesting. however if your not confident and don't have a test cluster to try this on before i would wait for the kolla-ansible team or some operators that run a kolla cloud to chime in.
Will I get the templates and images back?
pull will cause new docker images to be pulled to all the nodes and they will be tagged with latest ectra. if you look at your /etc/kolla/global.yaml the tag that is uses will likely be something like this 2025.1-ubuntu-noble depending on what you set # Valid options are ['centos', 'debian', 'rocky', 'ubuntu'] #kolla_base_distro: "rocky" # Do not override this unless you know what you are doing. #openstack_release: "master" too https://github.com/openstack/kolla-ansible/blob/stable/2025.1/etc/kolla/glob... you local tagged images will be update to point to the latest version https://quay.io/repository/openstack.kolla/nova-compute?tab=tags when you do deploy it will go though the same steps in the same order as your initial deployment and will update all the config and deploy the new contienrs using the images you pulled. this is intended to be non destructive in kolla. any vms ectra or glance images or cidner volumes should still exist after. you do not technically need to do stop first by the way. my main recommendation was to just make sure you are running the latest epoxy version of kolla-ansible and the latest epoxy version of openstack containers before debugging the placement issue to much further. you could instead just do kolla-ansible reconfigure -I multinode -t placement to see if that will fix the placement container issue and then see of that allows nova to start.
Franck
Le 18 juil. 2025 à 16:50, Sean Mooney <smooney@redhat.com> a écrit :
so just a suggestion
i would basiclly try turning it off and on a agin.
so i think the problem is that you limit the reconfig to nova but the srrro seam to indicate they placement is not runing or it not a new enough verions.
so in epoxy i belive kolla has a stop command
so i woudl be tempted to do a stop, pull the latest version of the kolla images with the pull action and then do anohter deploy rather then reconfigure.
recornigure at least in the past is actully just ment to update the config file and restart the contiers in place.
deploy does that but it can also update to newever version fo the images if you pull them first.
i have not worked on kolla in a very long time nad i rearly update my home deployment so the kolla team may have a better suggestion but
that would be what i tired if it was my home cluster.
note that when doing deploy i woudl allow it to run for all service his is effectivly jsut doing a mindor update to latest stable release of epoxy.
i would also make sure your kolla-ansible is using the latest epoxy version too incase your are hitting a fix know issue. thre is now a 20.1.0 aviable.
if your using it form git you can obviously just do a git pull but done forget to make sure you updated the deps
pip3 install --upgrade 'ansible-core>=2.17,<2.18.99' kolla-ansible==20.1.0 kolla-ansible install-deps
i think the root of your problem is with the fact palcement is not starting properly adn returnningn 500s
the python application found error i think is because of setuptools 80 and the the way the wsig script used to be generate becore we added a pyrpoject.toml
so im hoping using the latest images will have that resolved.
my home clustier is still on caracal and i need to upgrade it soon but i cant confirm if that will solve the issue but it likely that it will.
Thanks again. Now rabbitmq is the problem. TASK [rabbitmq : Waiting for rabbitmq to start] ******************************** fatal: [ordi1]: FAILED! => {"changed": true, "cmd": ["docker", "exec", "rabbitmq", "rabbitmqctl", "wait", "--timeout", "60", "/var/lib/rabbitmq/mnesia/rabbitmq.pid"], "delta": "0:05:10.503808", "end": "2025-07-18 18:33:28.522700", "msg": "non-zero return code", "rc": 69, "start": "2025-07-18 18:28:18.018892", "stderr": "Error:\nrabbit_is_not_running", "stderr_lines": ["Error:", "rabbit_is_not_running"], "stdout": "Waiting for pid file '/var/lib/rabbitmq/mnesia/rabbitmq.pid' to appear\npid is 1668\nWaiting for erlang distribution on node 'rabbit@ordi1' while OS process '1668' is running\nWaiting for applications 'rabbit_and_plugins' to start on node 'rabbit@ordi1'", "stdout_lines": ["Waiting for pid file '/var/lib/rabbitmq/mnesia/rabbitmq.pid' to appear", "pid is 1668", "Waiting for erlang distribution on node 'rabbit@ordi1' while OS process '1668' is running", "Waiting for applications 'rabbit_and_plugins' to start on node 'rabbit@ordi1' »]} Thanks again. (venv2) user1@ordi1:~/OPENSTACK/INSTALL$ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES fd06eabb8aab quay.io/openstack.kolla/rabbitmq:2025.1-ubuntu-noble "dumb-init --single-…" 35 minutes ago Up 2 minutes (unhealthy) rabbitmq (venv2) user1@ordi1:~/OPENSTACK/INSTALL$ docker logs rabbitmq …. BOOT FAILED =========== Timeout contacting cluster nodes: [rabbit@ordi4]. BACKGROUND ========== This cluster node was shut down while other nodes were still running. To avoid losing data, you should start the other nodes first, then start this one. To force this node to start, first invoke "rabbitmqctl force_boot". If you do so, any changes made on other cluster nodes after this one was shut down may be lost. DIAGNOSTICS =========== attempted to contact: [rabbit@ordi4] rabbit@ordi4: * unable to connect to epmd (port 4369) on ordi4: address (cannot connect to host/port) File multinode: [control] # These hostname must be resolvable from your deployment host ordi1 become=true ansible_become_password=XXXXXX ordi4 become=true ansible_become_password=XXXXXX I don't really know what to do, computer1 and computer4 communicate First time I have problems with rabbitmq. Franck
Le 18 juil. 2025 à 17:42, Sean Mooney <smooney@redhat.com> a écrit :
On 18/07/2025 16:20, Franck VEDEL (UGA) wrote:
Thansk a lot for your help.
I'm afraid of making a mistake...
Are the different operations the following:
kolla-ansible -i multinode stop pip3 install --upgrade 'ansible-core>=2.17,<2.18.99' kolla-ansible==20.1.0 kolla-ansible install-deps kolla-ansible -i multinode pull kolla-ansible -i multinode deploy
yes those are the steps i was suggesting.
however if your not confident and don't have a test cluster to try this on before i would wait for the kolla-ansible team or some operators that run a kolla cloud to chime in.
Will I get the templates and images back?
pull will cause new docker images to be pulled to all the nodes and they will be tagged with latest ectra.
if you look at your /etc/kolla/global.yaml
the tag that is uses will likely be something like this 2025.1-ubuntu-noble
depending on what you set
# Valid options are ['centos', 'debian', 'rocky', 'ubuntu'] #kolla_base_distro: "rocky"
# Do not override this unless you know what you are doing. #openstack_release: "master"
too https://github.com/openstack/kolla-ansible/blob/stable/2025.1/etc/kolla/glob...
you local tagged images will be update to point to the latest version
https://quay.io/repository/openstack.kolla/nova-compute?tab=tags
when you do deploy it will go though the same steps in the same order as your initial deployment
and will update all the config and deploy the new contienrs using the images you pulled.
this is intended to be non destructive in kolla.
any vms ectra or glance images or cidner volumes should still exist after.
you do not technically need to do stop first by the way.
my main recommendation was to just make sure you are running the latest epoxy version of kolla-ansible and the latest epoxy version of openstack containers
before debugging the placement issue to much further.
you could instead just do
kolla-ansible reconfigure -I multinode -t placement
to see if that will fix the placement container issue and then see of that allows nova to start.
Franck
Le 18 juil. 2025 à 16:50, Sean Mooney <smooney@redhat.com> a écrit :
so just a suggestion
i would basiclly try turning it off and on a agin.
so i think the problem is that you limit the reconfig to nova but the srrro seam to indicate they placement is not runing or it not a new enough verions.
so in epoxy i belive kolla has a stop command
so i woudl be tempted to do a stop, pull the latest version of the kolla images with the pull action and then do anohter deploy rather then reconfigure.
recornigure at least in the past is actully just ment to update the config file and restart the contiers in place.
deploy does that but it can also update to newever version fo the images if you pull them first.
i have not worked on kolla in a very long time nad i rearly update my home deployment so the kolla team may have a better suggestion but
that would be what i tired if it was my home cluster.
note that when doing deploy i woudl allow it to run for all service his is effectivly jsut doing a mindor update to latest stable release of epoxy.
i would also make sure your kolla-ansible is using the latest epoxy version too incase your are hitting a fix know issue. thre is now a 20.1.0 aviable.
if your using it form git you can obviously just do a git pull but done forget to make sure you updated the deps
pip3 install --upgrade 'ansible-core>=2.17,<2.18.99' kolla-ansible==20.1.0 kolla-ansible install-deps
i think the root of your problem is with the fact palcement is not starting properly adn returnningn 500s
the python application found error i think is because of setuptools 80 and the the way the wsig script used to be generate becore we added a pyrpoject.toml
so im hoping using the latest images will have that resolved.
my home clustier is still on caracal and i need to upgrade it soon but i cant confirm if that will solve the issue but it likely that it will.
It Works !!!! Thanks a lot Sean . You helped me so much with this problem. Thank you so much. I will test again all the services I want (eg vpnaas, designate) but I am optimistic!! Franck
Le 18 juil. 2025 à 19:08, Franck VEDEL (UGA) <franck.vedel@univ-grenoble-alpes.fr> a écrit :
Thanks again. Now rabbitmq is the problem. TASK [rabbitmq : Waiting for rabbitmq to start] ******************************** fatal: [ordi1]: FAILED! => {"changed": true, "cmd": ["docker", "exec", "rabbitmq", "rabbitmqctl", "wait", "--timeout", "60", "/var/lib/rabbitmq/mnesia/rabbitmq.pid"], "delta": "0:05:10.503808", "end": "2025-07-18 18:33:28.522700", "msg": "non-zero return code", "rc": 69, "start": "2025-07-18 18:28:18.018892", "stderr": "Error:\nrabbit_is_not_running", "stderr_lines": ["Error:", "rabbit_is_not_running"], "stdout": "Waiting for pid file '/var/lib/rabbitmq/mnesia/rabbitmq.pid' to appear\npid is 1668\nWaiting for erlang distribution on node 'rabbit@ordi1' while OS process '1668' is running\nWaiting for applications 'rabbit_and_plugins' to start on node 'rabbit@ordi1'", "stdout_lines": ["Waiting for pid file '/var/lib/rabbitmq/mnesia/rabbitmq.pid' to appear", "pid is 1668", "Waiting for erlang distribution on node 'rabbit@ordi1' while OS process '1668' is running", "Waiting for applications 'rabbit_and_plugins' to start on node 'rabbit@ordi1' »]}
Thanks again. (venv2) user1@ordi1:~/OPENSTACK/INSTALL$ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES fd06eabb8aab quay.io/openstack.kolla/rabbitmq:2025.1-ubuntu-noble "dumb-init --single-…" 35 minutes ago Up 2 minutes (unhealthy) rabbitmq
(venv2) user1@ordi1:~/OPENSTACK/INSTALL$ docker logs rabbitmq …. BOOT FAILED =========== Timeout contacting cluster nodes: [rabbit@ordi4].
BACKGROUND ==========
This cluster node was shut down while other nodes were still running. To avoid losing data, you should start the other nodes first, then start this one. To force this node to start, first invoke "rabbitmqctl force_boot". If you do so, any changes made on other cluster nodes after this one was shut down may be lost.
DIAGNOSTICS ===========
attempted to contact: [rabbit@ordi4]
rabbit@ordi4: * unable to connect to epmd (port 4369) on ordi4: address (cannot connect to host/port)
File multinode: [control] # These hostname must be resolvable from your deployment host ordi1 become=true ansible_become_password=XXXXXX ordi4 become=true ansible_become_password=XXXXXX
I don't really know what to do, computer1 and computer4 communicate
First time I have problems with rabbitmq.
Franck
Le 18 juil. 2025 à 17:42, Sean Mooney <smooney@redhat.com> a écrit :
On 18/07/2025 16:20, Franck VEDEL (UGA) wrote:
Thansk a lot for your help.
I'm afraid of making a mistake...
Are the different operations the following:
kolla-ansible -i multinode stop pip3 install --upgrade 'ansible-core>=2.17,<2.18.99' kolla-ansible==20.1.0 kolla-ansible install-deps kolla-ansible -i multinode pull kolla-ansible -i multinode deploy
yes those are the steps i was suggesting.
however if your not confident and don't have a test cluster to try this on before i would wait for the kolla-ansible team or some operators that run a kolla cloud to chime in.
Will I get the templates and images back?
pull will cause new docker images to be pulled to all the nodes and they will be tagged with latest ectra.
if you look at your /etc/kolla/global.yaml
the tag that is uses will likely be something like this 2025.1-ubuntu-noble
depending on what you set
# Valid options are ['centos', 'debian', 'rocky', 'ubuntu'] #kolla_base_distro: "rocky"
# Do not override this unless you know what you are doing. #openstack_release: "master"
too https://github.com/openstack/kolla-ansible/blob/stable/2025.1/etc/kolla/glob...
you local tagged images will be update to point to the latest version
https://quay.io/repository/openstack.kolla/nova-compute?tab=tags
when you do deploy it will go though the same steps in the same order as your initial deployment
and will update all the config and deploy the new contienrs using the images you pulled.
this is intended to be non destructive in kolla.
any vms ectra or glance images or cidner volumes should still exist after.
you do not technically need to do stop first by the way.
my main recommendation was to just make sure you are running the latest epoxy version of kolla-ansible and the latest epoxy version of openstack containers
before debugging the placement issue to much further.
you could instead just do
kolla-ansible reconfigure -I multinode -t placement
to see if that will fix the placement container issue and then see of that allows nova to start.
Franck
Le 18 juil. 2025 à 16:50, Sean Mooney <smooney@redhat.com> a écrit :
so just a suggestion
i would basiclly try turning it off and on a agin.
so i think the problem is that you limit the reconfig to nova but the srrro seam to indicate they placement is not runing or it not a new enough verions.
so in epoxy i belive kolla has a stop command
so i woudl be tempted to do a stop, pull the latest version of the kolla images with the pull action and then do anohter deploy rather then reconfigure.
recornigure at least in the past is actully just ment to update the config file and restart the contiers in place.
deploy does that but it can also update to newever version fo the images if you pull them first.
i have not worked on kolla in a very long time nad i rearly update my home deployment so the kolla team may have a better suggestion but
that would be what i tired if it was my home cluster.
note that when doing deploy i woudl allow it to run for all service his is effectivly jsut doing a mindor update to latest stable release of epoxy.
i would also make sure your kolla-ansible is using the latest epoxy version too incase your are hitting a fix know issue. thre is now a 20.1.0 aviable.
if your using it form git you can obviously just do a git pull but done forget to make sure you updated the deps
pip3 install --upgrade 'ansible-core>=2.17,<2.18.99' kolla-ansible==20.1.0 kolla-ansible install-deps
i think the root of your problem is with the fact palcement is not starting properly adn returnningn 500s
the python application found error i think is because of setuptools 80 and the the way the wsig script used to be generate becore we added a pyrpoject.toml
so im hoping using the latest images will have that resolved.
my home clustier is still on caracal and i need to upgrade it soon but i cant confirm if that will solve the issue but it likely that it will.
Hi Everyone, We are trying to install Cloud Kitty for the pricing model, and the GUI is as mentioned below. Please let us know how to resolve this issue. [image: image.png] thanks, TRB.
Hi Community, We have added the Logs for reference. (venv) xxx@openstack-aio-01:~$ docker exec -it horizon curl http://cloudkitty:8889/v1/rating/modules curl: (6) Could not resolve host: cloudkitty curl: (6) Could not resolve host: cloudkitty curl: (6) Could not resolve host: cloudkitty curl: (6) Could not resolve host: cloudkitty curl: (6) Could not resolve host: cloudkitty curl: (6) Could not resolve host: cloudkitty curl (http://cloudkitty:8889/v1/rating/modules): response: 000, time: 2.699146, size: 0 (venv) xxx@openstack-aio-01:~$ docker exec -it horizon curl http://cloudkitty:8889/v1/rating/modules curl: (6) Could not resolve host: cloudkitty curl: (6) Could not resolve host: cloudkitty curl: (6) Could not resolve host: cloudkitty curl: (6) Could not resolve host: cloudkitty curl: (6) Could not resolve host: cloudkitty curl: (6) Could not resolve host: cloudkitty curl (http://cloudkitty:8889/v1/rating/modules): response: 000, time: 2.430907, size: 0 Thanks, TRB. On Fri, Jul 18, 2025 at 8:41 PM TRB PREM KUMAR <kumar6009@gmail.com> wrote:
Hi Everyone,
We are trying to install Cloud Kitty for the pricing model, and the GUI is as mentioned below.
http://192.168.58.12/admin/hashmap/ Something went wrong! An unexpected error has occurred. Try refreshing the page. If that doesn't help, contact your local administrator.
Please let us know how to resolve this issue. Thanks, TRB.
Hi, We have the share the error logs for the URL: http://192.168.58.12/admin/hashmap/ root@openstack-aio-01:/var/lib/docker/volumes/kolla_logs/_data/horizon# tail -f horizon-error.log 2025-07-25 09:16:18.511651 handled = self.handle_table(table) 2025-07-25 09:16:18.511665 File "/var/lib/kolla/venv/lib/python3.9/site-packages/horizon/tables/views.py", line 122, in handle_table 2025-07-25 09:16:18.511673 data = self._get_data_dict() 2025-07-25 09:16:18.511676 File "/var/lib/kolla/venv/lib/python3.9/site-packages/horizon/tables/views.py", line 251, in _get_data_dict 2025-07-25 09:16:18.511678 self._data = {self.table_class._meta.name: self.get_data()} 2025-07-25 09:16:18.511682 File "/var/lib/kolla/venv/lib/python3.9/site-packages/cloudkittydashboard/dashboards/admin/hashmap/views.py", line 42, in get_data 2025-07-25 09:16:18.511689 service = manager.info.get_metric(metric_name=s['name']) 2025-07-25 09:16:18.511721 File "/var/lib/kolla/venv/lib/python3.9/site-packages/cloudkittyclient/utils.py", line 71, in wrap 2025-07-25 09:16:18.511728 raise http.HttpError(message=e.response.text, 2025-07-25 09:16:18.511731 keystoneauth1.exceptions.http.HttpError: {"faultcode": "Client", "faultstring": "compute", "debuginfo": null} (HTTP 404) 2025-07-25 09:27:30.554792 Internal Server Error: /admin/hashmap/ 2025-07-25 09:27:30.554816 Traceback (most recent call last): 2025-07-25 09:27:30.554819 File "/var/lib/kolla/venv/lib/python3.9/site-packages/cloudkittyclient/utils.py", line 69, in wrap 2025-07-25 09:27:30.554822 return func(*args, **kwargs) 2025-07-25 09:27:30.554824 File "/var/lib/kolla/venv/lib/python3.9/site-packages/cloudkittyclient/v1/info.py", line 32, in get_metric 2025-07-25 09:27:30.554826 return self.api_client.get(url).json() 2025-07-25 09:27:30.554828 File "/var/lib/kolla/venv/lib/python3.9/site-packages/keystoneauth1/adapter.py", line 393, in get 2025-07-25 09:27:30.554831 return self.request(url, 'GET', **kwargs) 2025-07-25 09:27:30.554833 File "/var/lib/kolla/venv/lib/python3.9/site-packages/keystoneauth1/adapter.py", line 255, in request 2025-07-25 09:27:30.554835 return self.session.request(url, method, **kwargs) 2025-07-25 09:27:30.554837 File "/var/lib/kolla/venv/lib/python3.9/site-packages/keystoneauth1/session.py", line 985, in request 2025-07-25 09:27:30.554839 raise exceptions.from_response(resp, method, url) 2025-07-25 09:27:30.554842 keystoneauth1.exceptions.http.NotFound: Unrecognized schema in response body. (HTTP 404) (Request-ID: req-4511cff1-77e3-4cc6-9ec1-f2d8057c368c) 2025-07-25 09:27:30.554844 2025-07-25 09:27:30.554846 During handling of the above exception, another exception occurred: 2025-07-25 09:27:30.554848 2025-07-25 09:27:30.554850 Traceback (most recent call last): 2025-07-25 09:27:30.554853 File "/var/lib/kolla/venv/lib64/python3.9/site-packages/django/core/handlers/exception.py", line 55, in inner 2025-07-25 09:27:30.554855 response = get_response(request) 2025-07-25 09:27:30.554857 File "/var/lib/kolla/venv/lib64/python3.9/site-packages/django/core/handlers/base.py", line 197, in _get_response 2025-07-25 09:27:30.554860 response = wrapped_callback(request, *callback_args, **callback_kwargs) 2025-07-25 09:27:30.554862 File "/var/lib/kolla/venv/lib/python3.9/site-packages/horizon/decorators.py", line 51, in dec 2025-07-25 09:27:30.554864 return view_func(request, *args, **kwargs) 2025-07-25 09:27:30.554866 File "/var/lib/kolla/venv/lib/python3.9/site-packages/horizon/decorators.py", line 35, in dec 2025-07-25 09:27:30.554868 return view_func(request, *args, **kwargs) 2025-07-25 09:27:30.554871 File "/var/lib/kolla/venv/lib/python3.9/site-packages/horizon/decorators.py", line 35, in dec 2025-07-25 09:27:30.554873 return view_func(request, *args, **kwargs) 2025-07-25 09:27:30.554875 File "/var/lib/kolla/venv/lib/python3.9/site-packages/horizon/decorators.py", line 111, in dec 2025-07-25 09:27:30.554877 return view_func(request, *args, **kwargs) 2025-07-25 09:27:30.554880 File "/var/lib/kolla/venv/lib64/python3.9/site-packages/django/views/generic/base.py", line 104, in view 2025-07-25 09:27:30.554883 return self.dispatch(request, *args, **kwargs) 2025-07-25 09:27:30.554901 File "/var/lib/kolla/venv/lib64/python3.9/site-packages/django/views/generic/base.py", line 143, in dispatch 2025-07-25 09:27:30.554905 return handler(request, *args, **kwargs) 2025-07-25 09:27:30.554908 File "/var/lib/kolla/venv/lib/python3.9/site-packages/horizon/tables/views.py", line 222, in get 2025-07-25 09:27:30.554911 handled = self.construct_tables() 2025-07-25 09:27:30.554912 File "/var/lib/kolla/venv/lib/python3.9/site-packages/horizon/tables/views.py", line 213, in construct_tables 2025-07-25 09:27:30.554914 handled = self.handle_table(table) 2025-07-25 09:27:30.554916 File "/var/lib/kolla/venv/lib/python3.9/site-packages/horizon/tables/views.py", line 122, in handle_table 2025-07-25 09:27:30.554918 data = self._get_data_dict() 2025-07-25 09:27:30.554919 File "/var/lib/kolla/venv/lib/python3.9/site-packages/horizon/tables/views.py", line 251, in _get_data_dict 2025-07-25 09:27:30.554921 self._data = {self.table_class._meta.name: self.get_data()} 2025-07-25 09:27:30.554923 File "/var/lib/kolla/venv/lib/python3.9/site-packages/cloudkittydashboard/dashboards/admin/hashmap/views.py", line 42, in get_data 2025-07-25 09:27:30.554925 service = manager.info.get_metric(metric_name=s['name']) 2025-07-25 09:27:30.554927 File "/var/lib/kolla/venv/lib/python3.9/site-packages/cloudkittyclient/utils.py", line 71, in wrap 2025-07-25 09:27:30.554929 raise http.HttpError(message=e.response.text, 2025-07-25 09:27:30.554931 keystoneauth1.exceptions.http.HttpError: {"faultcode": "Client", "faultstring": "compute", "debuginfo": null} (HTTP 404) Thanks, TRB. On Sat, Jul 19, 2025 at 12:11 PM TRB PREM KUMAR <kumar6009@gmail.com> wrote:
Hi Community,
We have added the Logs for reference. (venv) xxx@openstack-aio-01:~$ docker exec -it horizon curl http://cloudkitty:8889/v1/rating/modules curl: (6) Could not resolve host: cloudkitty curl: (6) Could not resolve host: cloudkitty curl: (6) Could not resolve host: cloudkitty curl: (6) Could not resolve host: cloudkitty curl: (6) Could not resolve host: cloudkitty curl: (6) Could not resolve host: cloudkitty curl (http://cloudkitty:8889/v1/rating/modules): response: 000, time: 2.699146, size: 0
(venv) xxx@openstack-aio-01:~$ docker exec -it horizon curl http://cloudkitty:8889/v1/rating/modules curl: (6) Could not resolve host: cloudkitty curl: (6) Could not resolve host: cloudkitty curl: (6) Could not resolve host: cloudkitty curl: (6) Could not resolve host: cloudkitty curl: (6) Could not resolve host: cloudkitty curl: (6) Could not resolve host: cloudkitty curl (http://cloudkitty:8889/v1/rating/modules): response: 000, time: 2.430907, size: 0
Thanks, TRB.
On Fri, Jul 18, 2025 at 8:41 PM TRB PREM KUMAR <kumar6009@gmail.com> wrote:
Hi Everyone,
We are trying to install Cloud Kitty for the pricing model, and the GUI is as mentioned below.
http://192.168.58.12/admin/hashmap/ Something went wrong!
An unexpected error has occurred. Try refreshing the page. If that doesn't help, contact your local administrator.
Please let us know how to resolve this issue. Thanks, TRB.
participants (3)
-
Franck VEDEL (UGA)
-
Sean Mooney
-
TRB PREM KUMAR