Closed
Bug 1153972
Opened 10 years ago
Closed 10 years ago
Please deploy release 0.17.4 to loop-server PRODUCTION
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: rpapa, Assigned: bobm)
Details
Hi Bob, when you have a moment, would you pls deploy loop-server 0.17.4 to prod?
Let me know when the deed is done and I'll verify before DNS switch.
Thanks!
------------------
RELEASE NOTES
------------------
https://github.com/mozilla-services/loop-server/releases
COMPARISONS
https://github.com/mozilla-services/loop-server/compare/0.15.6...0.16.0
https://github.com/mozilla-services/loop-server/compare/0.16.0...0.17.0
https://github.com/mozilla-services/loop-server/compare/0.17.1...0.17.4
TAGS
https://github.com/mozilla-services/loop-server/releases/tag/0.17.4
https://github.com/mozilla-services/loop-server/commit/20be97391ebbb3236fb708aa5486af9d4a35a13d
CHANGELOG
0.17.4 (2015-04-09)
-------------------
- Downgrade request to 2.45.0, since later versions introduce a latency in our
requests.
0.17.3 (2015-03-31)
-------------------
- AWS driver did not take bucket configuration into account.
- Add a ``loop.`` prefix on not prefixed keys.
0.17.2 (2015-03-31)
-------------------
- Fix the configuration validator of the filestorage name for AWS.
0.17.1 (2015-03-26)
-------------------
- S3 bucket names can be defined in the configuration.
0.17.0 (2015-03-24)
-------------------
Breaking changes:
~~~~~~~~~~~~~~~~~
- Remove validation on room "status" action (Bug 1144851)
New features:
~~~~~~~~~~~~~
- Allow removal of transactions (MULTI) when sharding is enabled (#315)
- Add file system and S3 file storage mechanisms (Bug 1141105)
0.16.0 (2015-03-12)
-------------------
Breaking changes:
~~~~~~~~~~~~~~~~~
- Log the correct number of users in a room (Bug 1137882)
New features:
~~~~~~~~~~~~~
- Handle the status action (Bug 1137849)
- Added a command to count the number of FxA users (Bug 1125597)
- Log tokbox sessionIds associated to the rooms (Bug 1134886)
- Log current room connection id for GET / POSTS on /rooms/{token} (1134884)
- Log room participant identifier (Bug 1134884)
- Log number of participants for all room actions (Bug 1137886)
- Log the room token on room creation (Bug 1137883)
- Log user type (Bug 1140181)
Internal changes:
~~~~~~~~~~~~~~~~~
- Updated NPM dependencies;
- Updated linting rules;
- Loadtests can now precise the SIMPLE_PUSH_URL to use
| Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(bobm)
| Assignee | ||
Comment 1•10 years ago
|
||
Building a production stack now.
Assignee: nobody → bobm
Status: NEW → ASSIGNED
Flags: needinfo?(bobm)
| Reporter | ||
Comment 2•10 years ago
|
||
Had some challenges getting 0.17.4 deployed today, so We'll deploy 0.17.4 tomorrow (Tues, 4/14).
| Reporter | ||
Comment 3•10 years ago
|
||
Hi Bob,
I've placed several calls successfully using the 0.17.4 ELB (now that S3 buckets are fixed). Can you switch over DNS and re-verify?
Thanks!
Flags: needinfo?(bobm)
| Assignee | ||
Comment 4•10 years ago
|
||
Excellent, will switch the production DNS to production 0.17.4 stack (loop-server-app-2) from 0.15.6 stack (loop-server-app-3). That counter-intuitive stack numbering is the result of the roll-back yesterday.
Flags: needinfo?(bobm)
| Assignee | ||
Comment 5•10 years ago
|
||
DNS Change completed. Closing this bug.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 6•10 years ago
|
||
This change was rolled back due to changes in production traffic.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
| Assignee | ||
Comment 7•10 years ago
|
||
Opened 1154506 to investigate deployment issue.
| Reporter | ||
Comment 8•10 years ago
|
||
We're going to wontfix this release in favor of a 0.17.5 which adds additional error S3 error messages so we can track down the source of errors on the 0.17.4 rollout.
see:
Bug 1155346 - Please deploy release 0.17.5 to loop-server STAGE
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•