Error when using nova client - Unknown Error (HTTP 500)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Nova Compute Charm |
New
|
Undecided
|
Unassigned |
Bug Description
Unfortunately I did not get totally to the bottom of this issue and I don't have steps to reproduce either, but here's a summary of what happened.
I deployed focal-ussuri Openstack bundle [1] on the Openstack-backed juju (2.9.12) and everything worked fine. When I returned to the cloud the next day, I noticed that "nova" client fails with message
"ERROR (ClientException): Unknown Error (HTTP 500)"
Looking into the nova-related logs (compute/
2021-11-11 08:50:29.385 136452 ERROR oslo_service.
2021-11-11 08:50:29.385 136452 ERROR oslo_service.
2021-11-11 08:50:29.385 136452 ERROR oslo_service.
2021-11-11 08:50:29.385 136452 ERROR oslo_service.
2021-11-11 08:50:29.385 136452 ERROR oslo_service.
2021-11-11 08:50:29.385 136452 ERROR oslo_service.
2021-11-11 08:50:29.385 136452 ERROR oslo_service.
2021-11-11 08:50:29.385 136452 ERROR oslo_service.
2021-11-11 08:50:29.385 136452 ERROR oslo_service.
2021-11-11 08:50:29.385 136452 ERROR oslo_service.
2021-11-11 08:50:29.385 136452 ERROR oslo_service.
2021-11-11 08:50:29.385 136452 ERROR oslo_service.
2021-11-11 08:50:29.385 136452 ERROR oslo_service.
2021-11-11 08:50:29.385 136452 ERROR oslo_service.
2021-11-11 08:50:29.385 136452 ERROR oslo_service.
2021-11-11 08:50:29.385 136452 ERROR oslo_service.
2021-11-11 08:50:29.385 136452 ERROR oslo_service.
2021-11-11 08:50:29.385 136452 ERROR oslo_service.
I then noticed that "nova-mysql-router" unit was in the blocked state with message:
"Failed to connect to MySQL"
To resolve this, I tried to flush the hosts table in mysql [2] and restart services on the blocked "nova-mysql-router" unit. This helped me solve the problems with database and the unit got into active/idle state again. However problem with nova client persisted. I traced to problem to the "nova-api” apache vhost running on nova-cloud-
2021-11-11 13:03:25.018270 Traceback (most recent call last):
2021-11-11 13:03:25.018595 File "/usr/bin/
2021-11-11 13:03:25.018704 application = init_application()
2021-11-11 13:03:25.018862 File "/usr/lib/
2021-11-11 13:03:25.018959 return wsgi_app.
2021-11-11 13:03:25.019093 File "/usr/lib/
2021-11-11 13:03:25.019279 config.
2021-11-11 13:03:25.019507 File "/usr/lib/
2021-11-11 13:03:25.019650 log.register_
2021-11-11 13:03:25.019826 File "/usr/lib/
2021-11-11 13:03:25.019991 conf.register_
2021-11-11 13:03:25.020109 File "/usr/lib/
2021-11-11 13:03:25.020225 result = f(self, *args, **kwargs)
2021-11-11 13:03:25.020336 File "/usr/lib/
2021-11-11 13:03:25.020516 self.register_
2021-11-11 13:03:25.020675 File "/usr/lib/
2021-11-11 13:03:25.020781 return f(self, *args, **kwargs)
2021-11-11 13:03:25.020916 File "/usr/lib/
2021-11-11 13:03:25.021025 raise ArgsAlreadyPars
2021-11-11 13:03:25.021231 oslo_config.
I tried to poke around a bit and I ended up restarting the apache2 service which ultimately solved my issue with nova client. So while I don't have cause of this issue or reproducible steps, here's my workaround:
* Flush mysql “hosts” DB [2]
* Restart services on blocked mysql-router units (using juju actions)
* Restart apache2 service on nova-cloud-
---
[1] https:/
[2] https:/