Nova keypair for triple0 octavia deployment
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Triaged
|
Critical
|
Rohit Londhe |
Bug Description
TripleO deployment for Octavia getting failed because there is no valid Nova keypair
Considering the removal of Nova from undercloud/director node, there is no one who can generate a keypair, and the current Octavia deployment still thinks that it should get a keypair from Nova to work.
Below is the error message which we getting during deployment:
~~~
**kwargs)\n\n File \"/usr/
idate\n result = super(TemplateR
e-packages/
://192.
/deployment/
~~~
Deployment command:
~~~
[stack@standalone ~]$ sudo openstack tripleo deploy \
--templates \
--local-
-e /usr/share/
-r /usr/share/
-e /usr/share/
-e $HOME/container
-e $HOME/standalon
--output-dir $HOME \
--standalone
~~~
The highlighted section from the URL is getting called out for generating the keypair, https:/
https:/
There are a couple of workarounds like manually providing a public key or comment-out the keypair generation part itself.
Looking for a solution where we can seamlessly deploy Octavia
Additional details:
1. Provider driver - Amphora
2. Facing problem for standalone/
Changed in tripleo: | |
assignee: | nobody → Rohit Londhe (rohitl512) |
tags: | added: tripleo-heat-templates |
Changed in tripleo: | |
importance: | Undecided → Critical |
status: | New → Triaged |
milestone: | none → wallaby-2 |
Changed in tripleo: | |
milestone: | wallaby-2 → wallaby-3 |
Changed in tripleo: | |
milestone: | wallaby-3 → wallaby-rc1 |
Changed in tripleo: | |
milestone: | wallaby-rc1 → xena-1 |
Changed in tripleo: | |
milestone: | xena-1 → xena-2 |
Changed in tripleo: | |
milestone: | xena-2 → xena-3 |
So the problem is that we don't have Nova on the Director node in Tripleo. So we fail here: /opendev. org/openstack/ tripleo- heat-templates/ src/branch/ master/ deployment/ octavia/ octavia- deployment- config. j2.yaml# L208-L212
https:/
When we try to reach out to the non existent API endpoint. Then we use that param here: /opendev. org/openstack/ tripleo- heat-templates/ src/branch/ master/ deployment/ octavia/ octavia- deployment- config. j2.yaml# L227-L229
https:/
So this whole mechanism needs to be removed and replaced with something. I guess we would ideally do it with Ansible and generate a new key, then use that key during the deployment?