Updates to placement api fail if placement endpoint changes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Triaged
|
Undecided
|
Unassigned | ||
OpenStack Keystone Charm |
Fix Released
|
High
|
Liam Young | ||
OpenStack Nova Cloud Controller Charm |
Fix Released
|
High
|
Liam Young | ||
OpenStack Nova Compute Charm |
Invalid
|
Undecided
|
Unassigned |
Bug Description
If the url of the placement api changes after nova-compute has been started then placement updates fail as nova-compute appears to cache the old endpoint url.
To reproduce, update the placement endpoint to something incorrect in keystone and restart nova-compute. Errors contacting the placement api will be reported every minute or so. Now, correct the entry in keystone. The errors will continue despite the catalogue now being correct. Restarting nova-compute fixes the issue.
In my deployment this occurred when the placement end point switched from http to https after the nova-compute node had started. This resulted in the following in the nova-compute log:
2019-04-25 09:58:12.175 31793 ERROR nova.scheduler.
<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-04-25 09:58:12.176 31793 DEBUG oslo_concurrenc
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
2019-04-25 09:58:12.177 31793 ERROR nova.compute.
description: | updated |
Changed in nova: | |
assignee: | nobody → Liam Young (gnuoy) |
Changed in charm-nova-compute: | |
status: | New → Triaged |
Changed in charm-keystone: | |
milestone: | none → 20.10 |
Changed in charm-nova-cloud-controller: | |
milestone: | none → 20.10 |
Changed in charm-keystone: | |
status: | Fix Committed → Fix Released |
Changed in charm-nova-cloud-controller: | |
status: | Fix Committed → Fix Released |
What release is this?
What does your [placement] configuration in nova.conf on the compute host look like?
I'm wondering if keystoneauth1 is caching something about the endpoint URL?