Doesn't works with mesos 0.24

[altvnk]

Mesos 0.24 was released recently. Was not able to make it work with updated version. Marathon-consul don't have any information in log, even in debug mode, so i don't have any diagnostic information. After downgrading mesos it works as usual. Btw, marathon 0.11 was also released, so it would be reasonable to check compatibility too.

[altvnk]

UPDATE: marathon 0.11 seems working fine, tested just now

[Mongey]

:+1: marathon-consul doesn't seem to work using marathon 0.11 and 0.24.1

[abhishekamralkar]

do we have any deadline for this , we recently migrated to DCOS 1.3 and it uses Mesos 0.24.1 ,but marathon-consul not working with it. DO we have ay work around for it?

[BrianHicks]

@altvnk what version are you using? (0.1 and 0.2 are both released on the Docker index.) Can you make sure you're using the right debug flag? For 0.2 it should be --log-level=debug. Do you see any information about not being able to send events in the Marathon log?

[davidsayers]

I am encountering this issue with Marathon 0.13.0 and Mesos 0.25.0.

It looks like Consul DNS is returning the wrong IP:

# host marathon-consul.service.consul
marathon-consul.service.consul has address 172.17.0.1

After a redeploy of marathon-consul the information in the Consul KV is correctly updated. The wrong IP is causing problems when update events are sent to "http://marathon-consul.service.consul:31901/events"

I see that mesos-consul has a flag to set IP lookup order. I have tried various combinations of "--mesos-ip-order=host,mesos,netinfo,docker" but the issue is still present.

[ChrisAubuchon]

mesos-consul doesn't change the service if it already exists in Consul. The service will need to be deregistered and mesos-consul run with host first in the --mesos-ip-order list.

[davidsayers]

Its looking much healthier now. Thanks!