Problem :
Heat is incorrectly appending /v3 to the Keystone endpoint URL, even when it is already present. This results in a malformed URL, leading to communication issues during the creation of Kubernetes clusters with Magnum. The Keystone URL is determined by the server_keystone_endpoint_type setting in heat.conf.
Impact :
When a Heat stack is created, the VMs attempt to connect to the Keystone URL. If the URL contains a duplicate /v3, the connection fails, resulting in authorization errors. The following error message is logged in the VM:
Sep 30 05:19:40 new-cluster1-taypswwfmte6-master-0 heat-container-agent[2624]: Authorization failed: Not Found (HTTP 404) (Request-ID: req-108d6dda-f180-493a-ba10-4afb59ecfd56)
Sep 30 05:19:40 new-cluster1-taypswwfmte6-master-0 podman[2605]: /var/lib/os-collect-config/local-data not found. Skipping
This issue specifically occurs when the Keystone endpoint URL already ends with /v3, leading to stack creation failures.
Solution :
Currently I have implemented a fix in the sowm9802/heat repository and built a new Heat image to address this issue.
Problem : Heat is incorrectly appending /v3 to the Keystone endpoint URL, even when it is already present. This results in a malformed URL, leading to communication issues during the creation of Kubernetes clusters with Magnum. The Keystone URL is determined by the server_keystone_endpoint_type setting in heat.conf.
Impact : When a Heat stack is created, the VMs attempt to connect to the Keystone URL. If the URL contains a duplicate /v3, the connection fails, resulting in authorization errors. The following error message is logged in the VM:
This issue specifically occurs when the Keystone endpoint URL already ends with /v3, leading to stack creation failures.
Solution : Currently I have implemented a fix in the sowm9802/heat repository and built a new Heat image to address this issue.