search

ClusterHQ / flocker

Container data volume manager for your Dockerized application
https://clusterhq.com
Apache License 2.0
3.39k stars 290 forks source link

Flocker cannot attach openstack volume if instance use floating ip #1903

Open chernogorsky opened 9 years ago

chernogorsky commented 9 years ago

Hi, I have this configuration Flocker 1.2 Node: Centos 7 Control: Ubuntu 15.04 + unofficial cli Openstack: Kilo

Flocker-Instance (FI) Private IP Floating IP

Inside FI there is only Private IP (and services IPs)

When I have been trying to create dataset (using flocker-volumes ) I have received that log: Aug 31 06:12:23 docker-2-hoster.novalocal flocker-dataset-agent[8956]: {"api_ips": "{IPv4Address('XXX.XXX.XXX.114'): u'137e95d5-8c94-4c4f-aeb1-c2c4b9d5d933', IPv4Address('10.0.0.214'): u'243edf5d-1324-46a1-89ff-d55c106ff930', IPv4Address('10.0.0.216'): u'115fc519-c0f5-4c5f-a79c-a6625396a84b', IPv4Address('10.0.0.165'): u'b77a6529-2649-4ec7-bb71-38cb0805ab89', IPv4Address('XXX.XXX.XXX.121'): u'115fc519-c0f5-4c5f-a79c-a6625396a84b', IPv4Address('XXX.XXX.XXX.116'): u'b77a6529-2649-4ec7-bb71-38cb0805ab89', IPv4Address('10.0.0.215'): u'137e95d5-8c94-4c4f-aeb1-c2c4b9d5d933', IPv4Address('10.0.0.213'): u'9bfa678f-d6db-4473-9940-6315c917cf17'}", "task_uuid": "65debb45-2616-4d9c-b5d0-a34fecb269f1", "local_ips": "set([IPv4Address('127.0.0.1'), IPv6Address('fe80::f816:3eff:fe23:3b60'), IPv6Address('::1'), IPv4Address('172.17.42.1'), IPv4Address('10.0.0.216')])", "timestamp": 1441001543.45506, "message_type": "flocker:node:agents:blockdevice:openstack:compute_instance_id:not_found", "task_level": [2, 3]}

After some investigation, I have found that "problem" in this string (file flocker/node/agents/cinder.py) if api_addresses and api_addresses.issubset(local_ips):

I suppose, because, it tries to find all addresses (including floating ip) in the list of local ips After changing to this if api_addresses and len(api_addresses.intersection(local_ips)):

It start to work

itamarst commented 9 years ago

Thanks for the bug report and suggested fix, that does seem like a problem. I'll file a bug in our main issue tracker tomorrow morning so that the work to fix that gets scheduled.

itamarst commented 9 years ago

Done: https://clusterhq.atlassian.net/browse/FLOC-2966

wallnerryan commented 8 years ago

related to https://github.com/ClusterHQ/flocker/issues/2693

lmeyemezu commented 7 years ago

Is this bug corrected ? I encounter the same isue with flocker 1.15.0 and openstack kilo. Any idea ? Regards

gukai commented 7 years ago

https://github.com/gukai/flocker/commit/f29a0e74a1d984f5bd1a2b92334f875125a896a6

adamtheturtle commented 7 years ago

@gukai and @lmeyemezu Thank you for your interest in Flocker. ClusterHQ has shut down and is therefore not maintaining this repository. However, a group of ex-ClusterHQ employees is interested in maintaining Flocker and so I recommend that you get in touch with us - see https://www.scatterhq.com for details.