Brian Hicks created MESOS-825:
---------------------------------
Summary: Querying Slave Status uses wrong host
Key: MESOS-825
URL: https://issues.apache.org/jira/browse/MESOS-825
Project: Mesos
Issue Type: Bug
Components: webui
Affects Versions: 0.14.2, 0.14.0
Environment: Ubuntu 12.04, EC2, Vagrant
Reporter: Brian Hicks
Priority: Minor
What I do:
- Go to master's "slaves" tab
- Select an individual slave to view
What I expect:
- Slave status, logs, etc.
What I get:
- Red flash message that says "Failed to get slave usage / state: [object
Object]".
- When I inspect the requests from the Chrome dev tools, I see it's trying to
request the hostname of the node. E.G. on EC2, instead of
ec2-n-n-n-n.us-west-1.amazonaws.com:5051, it's requesting
ip-n-n-n-n.us-west-1.compute.internal:5051. When I run in vagrant, it uses the
hostname. Substituting the public host in the URLs works fine.
Other info:
- I'm running the mesosphere prepackaged distribution, but have also been able
to reproduce by running `mesos-master --cluster=batman --ip=192.168.1.104
--port=5050 --zk=zk://localhost:2181/mesos`
- This is consistent between AWS and Vagrant
Is there anything else you need from me, or am I just running Mesos incorrectly?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
