1024171 - Getting Invalid Partner Credentials trying to hit our partner from Loop-Server Stage

Status: VERIFIED FIXED

(Hello (Loop) :: Server, defect, P1)

Description

[James Bonacci [:jbonacci]]

So, just of the heck of it, :mostlygeek toggled /data/loop-server/config/settings.json on this most recent Stage deploy



But, when I try to hit the partner server with our loadtests "make test" command, I get 503s.

The loop_out.log file on the one AWS instance for our Stage environment, shows the following:
[Error: Failed to createSession. Error: An authentcation error occurred: (403) <?xml version="1.0" encoding="UTF-8" standalone="yes"?><errorPayload><code>-1</code><message>Invalid partner credentials</message></errorPayload>]

We can run from the mock server in the meantime.

Please investigate!


FYI: from the terminal/localhost side:
1 occurrences of: 
    AssertionError: 503 != 200    Traceback: 
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "loadtest.py", line 19, in test_all
    call_id, session, caller_token, api_key = self.initiate_call(token)
  File "loadtest.py", line 65, in initiate_call
    self.assertEquals(resp.status_code, 200)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/case.py", line 515, in assertEqual
    assertion_func(first, second, msg=msg)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/case.py", line 508, in _baseAssertEqual
    raise self.failureException(msg)

Comment 1

[Alexis Metaireau (:alexis)]

I think this is basically the same thing as bug 1023518, but it should be fixed by now.

If this is staging and pointing to the mantis server (their load environment), maybe that's because the credentials they gave us aren't valid anymore, or that they are experiencing problems.

Comment 2

[Alexis Metaireau (:alexis)]

I've sent a mail to them to check if the credentials we have are valid or not for staging, and to know if they're experiencing troubles. I'll put back their answer here.

Comment 3

[Alexis Metaireau (:alexis)]

After checking the configuration on staging, it seems that it's not using the right server url for tokbox. 

url should be set like:

> apiUrl = "http://mantis301-sat.tokbox.com:9999"

(note this is inside the tokbox config object).

When setting it to this value, though, it doesn't seems we're able to reach it, I'm getting
Error: Failed to createSession. Error: The request failed: Error: connect EHOSTUNREACH

So maybe their network is not reachable from our side.

I'll ask them more information about that.

Comment 4

[Alexis Metaireau (:alexis)]

Benson, can you update stage to use this config, they just told me they were blocking us until now.

Comment 5

[Benson Wong [:mostlygeek]]

Stage updated. I tested access to the endpoint: http://mantis301-sat.tokbox.com:9999 from the new server and the request is accepted.

Comment 6

[James Bonacci [:jbonacci]]

Good. We can call this Resolved and I will look at it more closely with this next deploy in bug 1024637.

Comment 7

[James Bonacci [:jbonacci]]

Actually, just going to close this.