Revision history [back]

click to hide/show revision 1
initial version

Hi fschaer,

Thank you for comment. The followings are results of my test according to your advices.

Recently I have upgraded my environment to Stein, but still I could not get Kubernetes up and running with Magnum... Regarding to your comment "try to re-enable certificate api", how did you re-enable it. Which command or configuration did you use?

In my case, I still got repeated message "waiting for CA to be made available for certificate manager api" even if added enable-cert-api-manager.sh as you advised. Although from cloud-init-output.log, this script did not run, but I also see problem is the following Heat template parameters are not passed from Magnum:

  • CA_KEY
  • OPENSTACK_CA

CA_KEY is used to store /etc/kubernetes/certs/ca.key file in enable-cert-api-manager.sh. So, if CA_KEY parameter is not fed like my case, heat template will not be successfully completed.

Did you manually create and feed CA_KEY data to Magnum template with some means?

Hi fschaer,

Thank you for comment. The followings are results of my test according to your advices.advice.

Recently I have upgraded my environment to Stein, but still I could not get Kubernetes up and running with Magnum... Regarding to your comment "try to re-enable certificate api", how did you re-enable it. Which command or configuration did you use?

In my case, I still got repeated message "waiting for CA to be made available for certificate manager api" even if added enable-cert-api-manager.sh as you advised. Although from cloud-init-output.log, this script did not run, but I also see problem is the following Heat template parameters are not passed from Magnum:

  • CA_KEY
  • OPENSTACK_CA

CA_KEY is used to store /etc/kubernetes/certs/ca.key file in by enable-cert-api-manager.sh. So, if CA_KEY parameter is not fed like my case, heat template will not be successfully completed.

Did you manually create and feed CA_KEY data to Magnum Heat template with some means?