Open Stack

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: failed (Result: exit-code) since mer. 2018-11-21 01:48:48 CET;
287ms ago
  Process: 13974 ExecStart=/usr/local/bin/kuryr-server --config-file
/etc/kuryr/kuryr.conf (code=exited, status=1/FAILURE)
 Main PID: 13974 (code=exited, status=1/FAILURE)

nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542 13974
ERROR kuryr     value = self._do_get(name, group, namespace)
nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542 13974
ERROR kuryr   File "/usr/lib/python2.7/dist-packages/oslo_config/cfg.py",
line 2942, in _
nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542 13974
ERROR kuryr     info = self._get_opt_info(name, group)
nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542 13974
ERROR kuryr   File "/usr/lib/python2.7/dist-packages/oslo_config/cfg.py",
line 3099, in _
nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542 13974
ERROR kuryr     raise NoSuchOptError(opt_name, group)
nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542 13974
ERROR kuryr NoSuchOptError: no such option driver in group [binding]
nov. 21 01:48:48 compute kuryr-server[13974]: 2018-11-21 01:48:48.542 13974
ERROR kuryr
nov. 21 01:48:48 compute systemd[1]: kuryr-libnetwork.service: Main process
exited, code=exited, status=1/FAILURE
nov. 21 01:48:48 compute systemd[1]: kuryr-libnetwork.service: Unit entered
failed state.
nov. 21 01:48:48 compute systemd[1]: kuryr-libnetwork.service: Failed with
result 'exit-code'.


and also the command lsof -iTCP -sTCP:LISTEN -P doesn't show the kuryr
service :
COMMAND    PID         USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
dockerd   1144         root    5u  IPv4  20120      0t0  TCP compute:2375
(LISTEN)
sshd      1288         root    3u  IPv4  19532      0t0  TCP *:22 (LISTEN)
sshd      1288         root    4u  IPv6  19534      0t0  TCP *:22 (LISTEN)
dnsmasq   1961       nobody    6u  IPv4  23450      0t0  TCP
192.168.122.1:53 (LISTEN)
sshd      4163       adouni    9u  IPv6  34950      0t0  TCP localhost:6010
(LISTEN)
sshd      4163       adouni   10u  IPv4  34951      0t0  TCP localhost:6010
(LISTEN)
qemu-syst 4621 libvirt-qemu   18u  IPv4  37121      0t0  TCP *:5900 (LISTEN)

!!!


Le mer. 21 nov. 2018 à 01:45, Jacob Burckhardt <jburckhardt at pdvwireless.com>
a écrit :

> 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:
>
>
>
> COMMAND    PID        USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
>
> …
>
> kuryr-ser 1976        root    6u  IPv4  30896      0t0  TCP
> localhost:23750 (LISTEN)
>
>
>
> So, you can see that kuryr is listening on 23750.  If lsof does not list a
> process listening on 23750, then check if kuryr is up by running:
>
>
>
> systemctl status kuryr-libnetwork
>
>
>
> You can also try restarting it by running:
>
>
>
> systemctl restart kuryr-libnetwork
>
>
>
> I installed that service by following:
>
>
>
>
> https://docs.openstack.org/kuryr-libnetwork/queens/install/compute-install-ubuntu.html
>
>
>
> That is the queens install guide which might help you since zun has no
> install guide in pike.
>
>
>
> If you see it listening, you can try this command:
>
>
>
> telnet 192.168.1.10 23750
>
>
>
> If it fails to connect, then try:
>
>
>
> telnet localhost 23750
>
>
>
> If it works with localhost but not 192.168.1.10, then I think that means
> you need to tell docker to connect to localhost instead of 192.168.1.10.
>
>
>
> Can you get the commands at the following web page to succeed?
>
>
>
> https://docs.openstack.org/kuryr-libnetwork/queens/install/verify.html
>
>
>
> *Jacob Burckhardt*
>
> Senior Software Engineer
>
> [image: pdvWireless]
>
>
>
> *From:* Rania Adouni <raniaadouni at gmail.com>
> *Sent:* Tuesday, November 20, 2018 2:02 PM
> *To:* openstack-dev at lists.openstack.org
> *Subject:* [openstack-dev] [zun] Failed to create Container
>
>
>
>
>
> Hi ,
>
>
>
> I am starting to use zun on openstack pike , and when I try to lunch
> container with cirros image , I get this reason : Docker internal error:
> 500 Server Error: Internal Server Error ("legacy plugin: Post
> http://192.168.1.10:23750/Plugin.Activate: dial tcp 192.168.1.10:23750:
> connect: connection refused").
>
> you can find here the log on my compute node :
> https://pastebin.com/nZTiTZiV.
>
> some help with this will be great .
>
> Best Regards,
>
> Rania Adouni
>
>
>
>
>
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20181121/21449ca1/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 2499 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20181121/21449ca1/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 2499 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20181121/21449ca1/attachment-0003.jpg>
-------------- next part --------------
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev