Cert generation fails is no public ipv4 specified
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Magnum | Status tracked in Rocky | |||||
Queens |
Triaged
|
Undecided
|
Unassigned | |||
Rocky |
In Progress
|
Undecided
|
Kien Nguyen |
Bug Description
Hello,
Faced the issue during the provisioning of a k8s cluster.
In case of provisioning a k8s cluster only in a private network without floating IPs, it appears impossible to generate the certificates because of a bug in make-cert.sh
https:/
public-ipv4 is not available in the metadata if no floating ip attached. As the outcome we got openssl command failed, because of the empty value for an IP statement in the subjectAltName
+ openssl req -new -days 1000 -key /etc/kubernetes
Error Loading request extension section req_ext
139869997266808
139869997266808
139869997266808
We should add a condition for this statement.
description: | updated |
In which magnum release you have this problem?