seting a container "v4-fixed-ip" doesn't work

[mhhli]

I try to set fixed ip for a container.
I run following command by zunclient:
      zun create --name test --cpu 2 --memory 4096 --security-group open --image-pull-policy ifnotpresent --image-driver glance --net network=c5bfb62c-5705-4b90-b23e-03948cdd8c3a,v4-fixed-ip=10.1.0.88 -i hadoop /bin/bash
I try to using "zun run",but after the container is runing ,the ip is 10.1.0.18 or others.
I can not confir this is a bug.
thanks.

[hongbin (hongbin034)]

Hi @mhhli,

Several questions for you:

* How do you install Zun (i.e. via Devstack)? If you install it from source, please provide your git commit (go to "/opt/stack/zun" and run this command: "git log -1")
* How do you install python-zunclient? If you install it from source, please provide your git commit as well (go to "/opt/stack/python-zunclient" and run this command: "git log -1")
* What is the output if you run this command:

  $ zun create --name test --cpu 2 --memory 4096 --security-group open --image-pull-policy ifnotpresent --image-driver glance --net network=c5bfb62c-5705-4b90-b23e-03948cdd8c3a,v4-fixed-ip=10.1.0.88 -i hadoop /bin/bash

* How your network "c5bfb62c-5705-4b90-b23e-03948cdd8c3a" was configured. Does it have a subnet to provide an IP address "10.1.0.88".
* Could you provide the logs of "zun-api" and "zun-compute" (if you installed Zun from devstack, run "journalctl -u devstack@zun* > zun.log").

[hongbin (hongbin034)]

Also, what is the output if you add "--debug" flag to the command:

  $ zun --debug create --name test --cpu 2 --memory 4096 --security-group open --image-pull-policy ifnotpresent --image-driver glance --net network=c5bfb62c-5705-4b90-b23e-03948cdd8c3a,v4-fixed-ip=10.1.0.88 -i hadoop /bin/bash

[mhhli (mssn)]

Hi @hongbin
Here is my answers.

* I install zun via kolla(Pike).I get kolla image from "http://tarballs.openstack.org/kolla/images/"(centos-source-registry-pike.tar.gz).
* I install zunclient from source. The follow is the output of command "git log -1":
      commit 3995efdc1f5eb6c8c583fe47ec315fa08585c7ff
      Author: Hongbin Lu <email address hidden>
      Date: Wed Oct 11 11:14:27 2017 -0400

      Enhance the README page

      Change-Id: Ic0e4f1da8530396f652b84d23dc705ff2ef69d6a
      (cherry picked from commit 0a7d2332fabfd7b103b033173e3dbe84ec183516)

* Here is the info about network:
 # openstack network list
 +--------------------------------------+---------------+--------------------------------------+
 | ID | Name | Subnets |
 +--------------------------------------+---------------+--------------------------------------+
 | c5bfb62c-5705-4b90-b23e-03948cdd8c3a | container-net | bf8e99c4-d8bb-4efa-a17a-e4dd6bfdf875 |
 +--------------------------------------+---------------+--------------------------------------+
 # openstack subnet list
 +--------------------------------------+------------------+--------------------------------------+-----------------+
 | ID | Name | Network | Subnet |
 +--------------------------------------+------------------+--------------------------------------+-----------------+
 | bf8e99c4-d8bb-4efa-a17a-e4dd6bfdf875 | container-subnet | c5bfb62c-5705-4b90-b23e-03948cdd8c3a | 10.1.0.0/24 |
 +--------------------------------------+------------------+--------------------------------------+-----------------+

* Here is the output about debug info and the logs of "zun-api" and "zun-compute". Also I give the "docker inspect" about the created container via zun.

 https://github.com/Mhhli/openstack_related.git

[hongbin (hongbin034)]

Hi mhhli,

Thanks for providing the detailed information. A few observations:

* Your log suggested you were using API version 1.4
* The kolla image name suggested you were using the Pike release (which is consistent with API version 1.4)

Then, it looks your Zun version is too old. The v4-fixed-ip support was landed after the pike release: https://review.openstack.org/#/c/504308/ . I think the issue will be fixed if you try a newer version of kolla image. If it doesn't work for you, I can try to work with kolla team to backport the v4-fixed-ip support to Pike.