Bug 1240123
Summary: | Openstack overcloud deploy, cannot do a successful update of a deployment | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Graeme Gillies <ggillies> |
Component: | openstack-tripleo-heat-templates | Assignee: | Jay Dobies <jason.dobies> |
Status: | CLOSED DUPLICATE | QA Contact: | yeylon <yeylon> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.0 (Kilo) | CC: | calfonso, jslagle, maufart, mburns, rhel-osp-director-maint, srevivo |
Target Milestone: | --- | Keywords: | Reopened, Triaged |
Target Release: | Director | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-07-08 14:59:29 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Graeme Gillies
2015-07-06 03:46:29 UTC
I suspect this is more the templates than the cli. *** This bug has been marked as a duplicate of bug 1240101 *** Are we sure this is a duplicate of 1240101? I'm not sure I understand how having the hard coded paths causes an update deploy to fail? Having a closer look at this today. If I run the following on the controller node os-apply-config --key hiera.datafiles --type raw --key-default '' this prints out the values that get mapped into data files (from my understanding). I can see that all the keystone ssl settings are indeed blank, which isn't great. Working back through the heat templates I see the value comes from KeystoneSigningKey which should be passed as an initial parameter to the heat stack create. When I do a heat stack-show overcloud I see the variable being passed in as a parameter "KeystoneSigningCertificate": "-----BEGIN CERTIFICATE-----\nMIIDJDCCAgygAwIBAgIBAjANBgkqhkiG9w0BAQUFADBTMQswCQYDVQQGEwJYWDEO\nMAwGA1UECBMFVW5zZXQxDjAMBgNVBAcTBVVuc2V0MQ4wDAYDVQQKEwVVbnNldDEU\nMBIGA1UEAxMLS2V5c3RvbmUgQ0EwHhcNMTUwNzA2MDUzNjQ5WhcNMjUwNzAzMDUz\nNjQ5WjBYMQswCQYDVQQGEwJYWDEOMAwGA1UECBMFVW5zZXQxDjAMBgNVBAcTBVVu\nc2V0MQ4wDAYDVQQKEwVVbnNldDEZMBcGA1UEAxMQS2V5c3RvbmUgU2lnbmluZzCC\nASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALnVp9z+sKx56LrQcbv6MsZh\nFJ3kQXxKbyF/lJER0rHAQ0s6rvbjrcyelXMmXXi9QCjgxRVoERroZPlU9yCj50EN\n+3+uI6bmGcEG8NgwvKGt+PVwqXwZpebdL5ZaoB+XYcSjxVHV+Cxw+LaYuAZa7pM/\ni0ADLlWs4B2g9Qkt9mD8G5nue769je0dknIn6bzDIdMZvN1ZMFEMGSm0KimF3CAN\n5ECicEPgsU3YM8QfNXd73/Fku4UlOqu33wB3ts2fpj0SnelUi42sX7tqEuVAdwFX\n5wN6Dgx7uf/BLjva9ghaqFoClUjp7wfXHrNwwNAxsyRv+wAoPtAi+erGj1TLidEC\nAwEAATANBgkqhkiG9w0BAQUFAAOCAQEALPAEkHKwqrihGPnLBIVbkFePRcv6yFcZ\nVqun+WLO7qh38YUo2GUeylLlbTj4SNkCpHHy+Hcqs42NSkyl5Y8rmWPvjvaCHjTi\nCsxAmD8TjnSghgwhU1LmxNDNcqPLIM4gsnNeVpBG9Lz7kkZ2BICDctDMNPvxF+4v\nZi8/PT/DS95ecpdieHu1U84dvJTwqKkAlBrg2QDWGvQofoyoBaECilOV7Qyy0iOm\nFPEuzeu9+7KOd86alhXvKLyVpJD4T5U7j5SqQTUwcU0UHFnxfNGZ7yABeR5UwKmc\nMcdroF1pOXDCHZuPn+QyaLQG9zWoRYZct9FQNgBVQ2tQmXEQViBh3Q==\n-----END CERTIFICATE-----\n" But for some reason it's not being picked up on the stack update I feel this is actually a bug either in the unified cli which is calling heat, or heat itself Regards, Graeme Submitted a fix that works for me https://review.gerrithub.io/#/c/238958/ marking as a duplicate of bug 1240461. They're fixed by the same patch *** This bug has been marked as a duplicate of bug 1240461 *** |