Openstack Kilo Nova-Docker:P of contanier will be lost after stop/start contanier via docker cli

Bug #1499381 reported by Xiao Li Xu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nova-docker
New
Undecided
Unassigned

Bug Description

Bug description:
  [Summary]
When stop container and restart container via docker cli (docker stop xx / docker start xx) on compute node, ip of this container will be lost. for detail pls refer following logs.
  [Topo]
  Unbuntu Kilo 14.04 OS , Kilo docker setup , 1 controller ,2 network node,6 computenode

  [Reproduceable or not]
  Can be reproduced,

  [Recreate Steps]

Meanwhile, we also tried these two ways to check if the container can get ip or not,
a, launch a new container, can get ip successfully;
b, stop and re-start via nova stop xxx / nova start xxx , container can get ip successfully.

# Steps:
1, Build up a openstack & docker setup based on Ubuntu 14.04 trusty;
2, 1 controller, 2 network node and 7 computer node ;
3, Launch docker containers;

root@quasarucn3:~# nova list
+--------------------------------------+--------------+---------+------------+-------------+---------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+--------------+---------+------------+-------------+---------------+
| ae6d1bc5-635a-453d-8cec-143a2b8240f6 | d7 | ACTIVE | - | Running | vmn=12.1.1.20 |
| 914c2f05-b56a-4689-9c1b-63f5bb36c7db | d8_sdn1 | ACTIVE | - | Running | vmn=12.1.1.22 |
| 925df284-3339-4af7-86e9-f66c41d947ce | d9_220 | ACTIVE | - | Running | vmn=12.1.1.26 |
| 518f7d49-07fb-474b-b18c-647d558562ea | d9_sdnve | ACTIVE | - | Running | vmn=12.1.1.25 |
| 59b3512a-8f6b-443d-ae1a-ca1ff615dba4 | leo_ubuntu | ACTIVE | - | Running | vmn=12.1.1.15 | <<<<<<<<<<<<<<<<<< container launched.
+--------------------------------------+--------------+---------+------------+-------------+---------------+
root@quasarucn3:~#

root@quasarsdn2:~# docker ps | grep 59b3512a-8f6b-443d-ae1a-ca1ff615dba4
90a1510e9dfd leo_ubuntu "/usr/sbin/sshd -D" 2 days ago Up 37 seconds nova-59b3512a-8f6b-443d-ae1a-ca1ff615dba4
root@quasarsdn2:~#

root@quasarsdn2:~# docker exec -i -t 90a1510e9dfd /bin/sh
# ifconfig
lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:65536 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

nsaeda5cee-7b Link encap:Ethernet HWaddr fa:16:3e:6c:88:96
          inet addr:12.1.1.15 Bcast:0.0.0.0 Mask:255.255.255.0 <<<<<<<<<<<<<<<<<<< ip got.
          inet6 addr: fe80::f816:3eff:fe6c:8896/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:648 (648.0 B) TX bytes:648 (648.0 B)

#
#

root@quasarsdn2:~# docker stop 90a1510e9dfd
90a1510e9dfd

root@quasarsdn2:~# docker start 90a1510e9dfd <<<<<<<<<<< stop then restart container.
90a1510e9dfd

root@quasarsdn2:~# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
c3464a45cd94 cirros "/sbin/init" 47 hours ago Up 23 minutes nova-ae6d1bc5-635a-453d-8cec-143a2b8240f6
90a1510e9dfd leo_ubuntu "/usr/sbin/sshd -D" 47 hours ago Up 16 seconds nova-59b3512a-8f6b-443d-ae1a-ca1ff615dba4
root@quasarsdn2:~#

root@quasarsdn2:~# docker exec -i -t 90a1510e9dfd /bin/sh
# ifconfig
# ifconfig <<<<<<<<<< no ip can be seen after container rebooting.
#

  [Log]
There is no error, this is docker related issue

Revision history for this message
Eugene Nikanorov (enikanorov) wrote :

Seems to be invalid for neutron

Changed in neutron:
status: New → Invalid
Revision history for this message
Xiao Li Xu (xiao-li-xu) wrote :

change it to nova-docker

affects: neutron → nova-docker
Changed in nova-docker:
status: Invalid → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.