no_proxy isn't correctly set if don't provide no_proxy when create baymodel

Bug #1493217 reported by Eli Qiao
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
New
Low
rajiv

Bug Description

no_proxy in swarm node is not correct if we don't pass no_proxy.

check the logic here: #https://github.com/openstack/magnum/blob/master/magnum/templates/docker-swarm/fragments/add-proxy.sh#L38

steps to reproduce:
magnum baymodel-create --name swarmmodel --image-id fedora-21-atomic-3 --keypair-id testkey --external-network-id $NIC_ID --dns-nameserver 10.248.2.5 --flavor-id m1.small --docker-volume-size 5 --coe swarm --fixed-network 192.168.0.0/24 --http-proxy http://10.239.4.160:911/ --https-proxy https://10.239.4.160:911/

magnum bay-create --name swarmbay --baymodel swarmmodel --node-count 2

login into swarm-master and swarm-node:
heat-parameter and no_proxy in /etc/bashrc is not correct

http://paste.openstack.org/show/449787/

Eli Qiao (taget-9)
Changed in magnum:
assignee: nobody → Eli Qiao (taget-9)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to magnum (master)

Fix proposed to branch: master
Review: https://review.openstack.org/221212

Changed in magnum:
status: New → In Progress
Revision history for this message
Eli Qiao (taget-9) wrote :
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on magnum (master)

Change abandoned by Adrian Otto (<email address hidden>) on branch: master
Review: https://review.openstack.org/221212
Reason: This patch has not seen any revisions in a long time. We want our review queue to contain active work-in-progress and code that reviewers are considering for merge. You are welcome to un-abandon this at any time, and continue making revisions.

Adrian Otto (aotto)
Changed in magnum:
milestone: none → mitaka-1
Changed in magnum:
importance: Undecided → Low
assignee: Eli Qiao (taget-9) → nobody
status: In Progress → New
rajiv (rajiv-kumar)
Changed in magnum:
assignee: nobody → rajiv (rajiv-kumar)
Revision history for this message
rajiv (rajiv-kumar) wrote :

For swarm, this issue is reproducible. When no no_proxy is not specified then it sets its own IP three, for exmaple

magnum cluster-template-show swarm-cluster-template-customized
+-----------------------+---------------------------------------------+
| Property | Value |
+-----------------------+---------------------------------------------+
| insecure_registry | - |
| labels | {'flannel_network_cidr': '192.168.10.0/24'} |
| updated_at | - |
| floating_ip_enabled | True |
| fixed_subnet | private-subnet |
| master_flavor_id | - |
| uuid | 025e2e73-3055-4f76-9033-a079c9262ce4 |
| no_proxy | - |
| https_proxy | - |
| tls_disabled | False |
| keypair_id | testkey |
| public | False |
| http_proxy | 172.30.66.104 |
| docker_volume_size | 5 |
| server_type | vm |
| external_network_id | public |
| cluster_distro | fedora-atomic |
| image_id | fedora-atomic-latest |
| volume_driver | - |
| registry_enabled | False |
| docker_storage_driver | devicemapper |
| apiserver_port | - |
| name | swarm-cluster-template-customized |
| created_at | 2016-09-06T03:24:58+00:00 |
| network_driver | docker |
| fixed_network | private |
| coe | swarm |
| flavor_id | m1.small |
| master_lb_enabled | False |
| dns_nameserver | 8.8.8.8 |
+-----------------------+---------------------------------------------+

And no_proxy is following in master node.
no_proxy="10.0.0.12,10.0.0.12,10.0.0.12".

And on swarm node
no_proxy="10.0.0.12,10.0.0.12,10.0.0.9"

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Change abandoned by Eli Qiao (<email address hidden>) on branch: master
Review: https://review.openstack.org/221212

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.