Rania,
For question #1, you can do the followings in *each compute node*:
* In your kuryr config file (i.e. /etc/kuryr/kuryr.conf), change the config
[DEFAULT]kuryr_uri . For example:
[DEFAULT]
kuryr_uri = http://192.168.1.10:23750
This config decides the IP address and port that the kuryr-libn
Hi Hongbin ,
thanks for your advice I did fix it with changing the kuryr-lib to 0.6.0
and my service just work fine and also with lsof -iTCP -sTCP:LISTEN -P
I can see it in the list :
*kuryr-ser 16581 root5u IPv4 91929 0t0 TCP
localhost:23750 (LISTEN)* > that is
Hi Hongbin,
Yes the version of kuryr-lib is :0.8.0 , So I think I should remove it !
I should remove only the kuryr-lib ! if you have some command they can help
me to unisntall it , it will be nice to provide it .
Best Regards,
Rania
Le mer. 21 nov. 2018 à 02:27, Hongbin Lu a écrit :
> Hi Ran
Hi Rania,
The config option 'driver' was recently renamed, so I guess the problem is
the version of kuryr-lib is not right. The Pike release of Zun is matched
to kuryr-lib 0.6.0 so you might want to confirm the version of kuryr-lib.
$ sudo pip freeze | grep kuryr
If the version is not right, uni
d, I guess they have defaults. I suggest commenting any
option that mentions "driver" and then restart kuryr-libnetwork.
-Jacob Burckhardt
From: Rania Adouni
Sent: Tuesday, November 20, 2018 4:58 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [zun] Failed to c
hi ,
Thanks for your reply and yes the problem that kuryr-libnetwork is failed
to start with the error :
● kuryr-libnetwork.service - Kuryr-libnetwork - Docker network plugin for
Neutron
Loaded: loaded (/etc/systemd/system/kuryr-libnetwork.service; enabled;
vendor preset: enabled)
Active: fa
Your error message says it cannot connect to port 23750. That's the
kuryr-libnetwork default listen port. On 192.168.1.10, run:
lsof -iTCP -sTCP:LISTEN -P
On my compute node, it outputs:
COMMANDPIDUSER FD TYPE DEVICE SIZE/OFF NODE NAME
…
kuryr-ser 1976root6u IPv4
