I investigated a bit on my side.

It seems it doesn't like the headers being sent from the new thrift lib
version in JS.


contentType: 'application/vnd.apache.thrift.json; charset=utf-8',

contentType: 'application/vnd.apache.thrift.json',

So it looks like the scheduler endpoint doesn't like the charset being

Tested this out on Safari and Firefox and it seems to resolve the issue and
it's probably not the right way to go about it but it might be a good
starting point.

On Tue, Feb 13, 2018 at 1:21 PM, Eyal Cidon <eci...@stanford.edu> wrote:

> Thank you for the prompt reply will try reverting to a version before the
> commit.
> Best,
> Eyal
> On Tue, Feb 13, 2018 at 1:18 PM, David McLaughlin <dmclaugh...@apache.org>
> wrote:
>> Hi Eyal,
>> This broke our cluster at Twitter too, so I think master is currently
>> broken. I think something went wrong with this commit:
>> https://github.com/apache/aurora/commit/cb0faf831747
>> baa93ba9cff2423862eccb9b99bb
>> I believe Jordan Ly and Stephan are discussing a remediation (i.e.
>> whether to revert or roll forward). Maybe they can update.
>> Cheers,
>> David
>> On Tue, Feb 13, 2018 at 11:38 AM, Eyal Cidon <eci...@stanford.edu> wrote:
>>> Hi all,
>>> I am trying to follow the instructions in these two guides:
>>> http://aurora.apache.org/documentation/latest/getting-started/vagrant/
>>> http://aurora.apache.org/documentation/latest/getting-started/tutorial/
>>> I am having issues with the vagrant VM, the aurora scheduler dash board
>>> get's stuck on loading and I can't figure out why. Also the Mesos agent is
>>> unreachable. I attached screen shots below.
>>> I am running this from my Mac, I cloned aurora from the github mirror
>>> and I made no modifications. My Vagrant is version 2.0.2 and VirtualBox is
>>> 5.2.6 guest edition.
>>> Would appreciate any help.
>>> Thank you,
>>> Eyal

Reply via email to