| Summary: | Export more flannel variables with flannel-docker container image | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Avesh Agarwal <avagarwa> |
| Component: | flannel-container | Assignee: | Avesh Agarwal <avagarwa> |
| Status: | CLOSED ERRATA | QA Contact: | Martin Jenner <mjenner> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.3 | CC: | cnegus, gscrivan, ypu |
| Target Milestone: | rc | Keywords: | Extras |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | flannel-docker-0.5.5-7 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-11-04 09:11:40 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Avesh Agarwal
2016-10-27 20:08:48 UTC
Hi Avesh, Do some tests they are passed, but seems the inspect info is not updated. Is this as expect? Details: Do following tests with other env options and it works well: 1. Config subnet.env and check it exist as we set. # docker run --privileged -d -v /usr:/mnt -e FLANNELD_ETCD_ENDPOINTS="http://172.17.0.2:2379" \ -e FLANNELD_ETCD_PREFIX="/atomic.io/netowork" \ -e FLANNELD_SUBNET_FILE="/root/flannel/subnet.env" \ flannel 2. Test multi-network with env options flannel docker cmds: # docker run --privileged -d -v /usr:/mnt -e FLANNELD_ETCD_ENDPOINTS="http://172.17.0.2:2379" -e FLANNELD_NETWORKS="red" flannel # docker run --privileged -d -v /usr:/mnt -e FLANNELD_ETCD_ENDPOINTS="http://172.17.0.2:2379" -e FLANNELD_NETWORKS="green" flannel # docker run --privileged -d -v /usr:/mnt -e FLANNELD_ETCD_ENDPOINTS="http://172.17.0.2:2379" -e FLANNELD_NETWORKS="green,blue" flannel 3. Test server/client mode with env options: # docker run --privileged -d -v /usr:/mnt -e FLANNELD_ETCD_ENDPOINTS="http://172.17.0.2:2379" -e FLANNELD_LISTEN="0.0.0.0:8888" flannel # docker run --privileged -d -v /usr:/mnt -e FLANNELD_ETCD_ENDPOINTS="http://172.17.0.2:2379" -e FLANNELD_REMOTE="172.17.0.7:8888" flannel But check the inspect info of the container, seems its still the same: "Env": [ "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin", "container=docker", "FLANNELD_ETCD_ENDPOINTS=http://127.0.0.1:2379", "FLANNELD_ETCD_PREFIX=/atomic.io/network" ], Joy, the changes are for only when flannel is used as system containers with atomic (--system flag or IOW with runc). Since docker allows -e option so this change is not needed, so this changes does not affect flannel functionality with docker in anyway. Thanks Avesh, So based on #comment4 use atomic install --system --set to test this image(flannel-docker-0.5.5-7) with multi-network case(which include on of the new options). The host can get ip as expect. Commands are as following: 1. install the flannel container in to hosts: # atomic install --system --name flannel-blue --set FLANNELD_NETWORKS="blue" 10.73.3.189:5000/flannel # atomic install --system --name flannel-blue-red --set FLANNELD_ETCD_ENDPOINTS="http://10.73.199.147:2379" --set FLANNELD_NETWORKS="blue,red" 10.73.3.189:5000/flannel 2. Start the flannel-blue and flannel-blue-red service 3. Use systemctl status to check the service status 4. Use ifconfig to check the interface and ip are set as expect. So this should work. Set it to verified. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:2650 |