[Openstack-operators] [kolla-ansible][octavia-role]

Flint WALRUS gael.therond at gmail.com
Tue Jul 17 19:29:30 UTC 2018


Oooooh! Ok! Thanks a lot for such information !! Indeed that was not clear
and didn’t make sens to me why each user should have to get it’s own ssh
key to log into the amphora!

You rocks guys, I’ll test that on tomorrow morning!

Thanks a lot!
G.
Le mar. 17 juil. 2018 à 18:55, Michael Johnson <johnsomor at gmail.com> a
écrit :

> Right. I am not familiar with the kolla role either, but you are
> correct.  The keypair created in nova needs to be "owned" by the
> octavia service account.
>
> Michael
> On Tue, Jul 17, 2018 at 9:07 AM iain MacDonnell
> <iain.macdonnell at oracle.com> wrote:
> >
> >
> >
> > On 07/17/2018 08:13 AM, Flint WALRUS wrote:
> > > Hi guys, I'm a trying to install Octavia as a new service on our cloud
> > > and facing few issues that I've been able to manage so far, until this
> > > nova-api keypair related issue.
> > >
> > > When creating a loadbalancer with the following command:
> > >
> > > openstack --os-cloud <MyCLOUD> loadbalancer create --name lb1
> > > --vip-network-id <NETID>
> > >
> > > My loadbalancer is in ERROR state with the following error from the
> NOVA
> > > API logs:
> > >
> > > 2018-07-17 14:03:58.721 25812 INFO nova.api.openstack.wsgi
> > > [req-69713077-c1e9-409a-9f9b-e3d5fb8006fc - - - - -] HTTP exception
> > > thrown: Invalid key_name provided.
> > >
> > > 2018-07-17 14:03:58.723 25812 INFO nova.osapi_compute.wsgi.server
> > > [req-69713077-c1e9-409a-9f9b-e3d5fb8006fc - - - - -]
> > > 10.1.0.10,172.21.0.21 "POST
> > > /v2.1/8dfa9231b14545bbab9d222c4425dd2f/servers HTTP/1.1" status: 400
> > > len: 489 time: 0.8432851
> > >
> > >  From my understanding of the nova-api source code it seems to be
> > > related to nova-api not being able to found out the expected ssh
> > > keypair, however if I'm doing:
> > >
> > > openstack --os-cloud <MyCLOUD> keypair list
> > >
> > > I'm correctly seing the octavia_ssh_key entry for my user.
> > >
> > > Has anyone already made it work using kolla?
> > > On a side note, I'm using stable/queens branch for both kolla docker
> > > images and kolla-ansible.
> >
> > Don't know how kolla handles it, but I'm fairly sure that the ssh key
> > has to be created/owned by the user that creates the amphora instances,
> > which is not the same as the user that creates the load-balancer. I
> > believe it's the user specified in the service_auth section of
> octavia.conf.
> >
> >      ~iain
> >
> > _______________________________________________
> > OpenStack-operators mailing list
> > OpenStack-operators at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20180717/bc454c75/attachment.html>


More information about the OpenStack-operators mailing list