Nova Scheduler caches placement URL
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Nova Cloud Controller Charm |
Triaged
|
High
|
Unassigned |
Bug Description
I have a Train deployment with the new placement charm and TLS enabled across the board with the help from the Vault charm and the certificates relation.
$ openstack catalog list
[ snip ]
| placement | placement | RegionOne |
| | | internal: https:/
| | | RegionOne |
| | | admin: https:/
| | | RegionOne |
| | | public: https:/
However, when creating a instance Nova attempts to contact the Placement API through a http url:
2019-10-18 14:41:50.422 146762 WARNING keystoneauth.
2019-10-18 14:41:50.427 146762 ERROR nova.scheduler.
Got 400: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>400 Bad Request</title>
</head><body>
<h1>Bad Request</h1>
<p>Your browser sent a request that this server could not understand.<br />
Reason: You're speaking plain HTTP to an SSL-enabled server port.<br />
Instead use the HTTPS scheme to access this URL, please.<br />
</p>
<hr>
<address>
</body></html>
.
2019-10-18 14:41:50.427 146762 INFO nova.scheduler.
It appears we need to coordinate a restart of the Nova Scheduler service after placement has configured TLS and has its URL set in the keystone catalog.
Changed in charm-nova-cloud-controller: | |
status: | New → Triaged |
importance: | Undecided → High |
I can also confirm that restarting the nova scheduler service resolves the situation and I can now create instances again.