Closed Bug 1085181 Opened 10 years ago Closed 10 years ago

Fix/Change config for Stage sync nodes to use hostnames rather than IPs

Categories

(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task, P2)

task

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jbonacci, Assigned: bobm)

References

Details

(Whiteboard: [qa+])

See https://github.com/mozilla-services/server-syncstorage/issues/22

For some reason, I can no longer do this to run a load test against a Stage sync node:
make megabench SERVER_URL=https://sync-1-us-east-1.stage.mozaws.net#SECRET

Now, I have to do this:
make megabench SERVER_URL=https://54.242.157.89#SECRET

Seems a change was made for better or worse to help Karl perform load testing while I was out on PTO.

What changes were made to Sync Stage to allow for IP use, but make it impossible to run tests using the host name?
:bobm
:rfkelly

so, if I try this now:
make test SERVER_URL=https://54.242.157.89#SECRET
from the server-syncstorage/loadtest directory, I get this:

1 occurrences of: 
    SSLError: hostname '54.242.157.89' doesn't match either of '*.stage.mozaws.net', 'stage.mozaws.net'    Traceback: 
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "stress.py", line 124, in test_storage_session
    response = self.session.get(url, **reqkwds)
  File "/Users/James/server-syncstorage/loadtest/lib/python2.7/site-packages/requests/sessions.py", line 469, in get
    return self.request('GET', url, **kwargs)
  File "/Users/James/server-syncstorage/loadtest/lib/python2.7/site-packages/loads/measure.py", line 80, in request
    method, url, headers=headers, **kwargs)
  File "/Users/James/server-syncstorage/loadtest/lib/python2.7/site-packages/requests/sessions.py", line 457, in request
    resp = self.send(prep, **send_kwargs)
  File "/Users/James/server-syncstorage/loadtest/lib/python2.7/site-packages/loads/measure.py", line 88, in send
    res = _Session.send(self, request, **kwargs)
  File "/Users/James/server-syncstorage/loadtest/lib/python2.7/site-packages/requests/sessions.py", line 569, in send
    r = adapter.send(request, **kwargs)
  File "/Users/James/server-syncstorage/loadtest/lib/python2.7/site-packages/requests/adapters.py", line 420, in send
    raise SSLError(e, request=request)


make: *** [test] Error 1


What gives?
Status: NEW → ASSIGNED
The tweak to allow IP-based loadtesting (by turning off SSL validation) was only made on the write-heavy-loadtest branch:

  https://github.com/mozilla-services/server-syncstorage/commit/f16a5e5229a920b56508c58222c48085377043f1

I can merge it across but I don't really know what's up with the IP-address thing and I don't want to make it the default if we don't have to.
Maybe there is more to this than I originally thought.
Well, since I have recent installs of browserid-verifier, tokenserver, msisdn-gateway, and loop-server, I tried the load tests for all of them. They all work great.

So, I may need to open a new issue in server-syncstorage to go with this bug.
We need to figure out why load testing Sync nodes no longer works at all.
And, that load testing tokenserver/sync nodes no longer works at all.

Weird.
We can do bug updates, or IRC, or a quick meeting, but I am still "blocked" on testing sync Stage because of this weirdness...
Flags: needinfo?(rfkelly)
Flags: needinfo?(bobm)
(In reply to James Bonacci [:jbonacci] from comment #4)
> We can do bug updates, or IRC, or a quick meeting, but I am still "blocked"
> on testing sync Stage because of this weirdness...

The actual fix here is to re-deploy Sync stage in the new development IAM.  We can't have alias records that point cross IAMs.
Flags: needinfo?(bobm)
Deferring needinfo? to :bobm
Flags: needinfo?(rfkelly)
Blocks: 1089945
Depends on: 1089944
OK. I am going to assume this is fixed via the new deployment: see bug 1089944
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.