Launch train for server-core 2.0 Features: This release updates account-portal to use the new server-core user libraries, including cached dn values which should reduce the number of ldap lookups. Tags: server-core: rpm-2.4-3 account-portal rpm-2.0-1 QA Plan: Needs full site testing of all functionality. We're totally swapping out the underlying user libraries. There should be no visible change (with the exception below) * Go to forgot-password page. Enter an email address and botch the captcha. The resulting page should correctly populate the email address, not the converted version. Ops Plan: This launch requires server-core 2.0+ and is now using those libraries. As a result, LDAP migration and syncNode updating are blockers for launch.
Bumping version requested to rpm-2.0-4 to incorporate the double-slash hotfix.
account portal version is now rpm-2.1-1 server-core is now rpm-2.6-1
Here's the sql for updating reset_codes: rename table reset_codes to reset_codes_old; create table reset_codes( username varchar(32) not null, product varchar(32) not null, reset varchar(32) default null, expiration datetime default null, PRIMARY KEY (`username`, `product`) ); insert into reset_codes(username, product, reset, expiration) select username, 'auth', reset, expiration from reset_codes_old where expiration > NOW(); (Note that this should be done right after the push, as the new primary key will reject the old submissions)
Component: Server: Account Portal → Operations: Deployment Requests
QA Contact: account-portal → operations-deploy-requests
Verified all account portal functionality works in test environment.
Assignee: nobody → petef
Status: NEW → ASSIGNED
Summary: Release train bug for server-core 2.0 → Release train bug for account-portal/server-core 2.0
build trouble: http://petef.pastebin.mozilla.org/1297133
dude pulled down the old lib. rpm-2.6-2 reflects this
Version bump to 2.6 is accidental, but we're keeping it :P
> make build build_rpms SERVER_CORE=rpm-2.6-1 ACCOUNT_PORTAL=rpm-2.6-2 deployed to stage
> * Go to forgot-password page. Enter an email address and botch the captcha. > The resulting page should correctly populate the email address, not the > converted version. https://stage-account.services.mozilla.com/forgot doesn't have captcha like the production version. Is there any way to verify this against stage?
Captcha is off for stage right now (see bug 678557).
There are a couple other issues related to clearing Sync data from the AP side. Symptom: "We had a problem purging the data from your account. Please try again later." Stage env Bugs opened by Pete: https://bugzilla.mozilla.org/show_bug.cgi?id=679500 https://bugzilla.mozilla.org/show_bug.cgi?id=679501 So, final "forgotten password" and clearing sync data verification will need to be done in Production.
And, adding one more for testing in Prod (due to same network issue): deleting an account.
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.