RPMs to be deployed: server-core rpm-1.7-1 Notable bugs: Bug 663911 - transitional writes to ldap for syncNode Bug 661247 - cleaned up encoding in mail headers QA plan: 1) Request a forgot password email. Check that to and from headers are correct. 2) Create a new account and get a node assignment. Check with ops to make sure that both primaryNode and syncNode have been written to in the LDAP record
Summary: Deploy server-core rpm-1.7 to stage and production → Deploy server-core rpm-1.7 to stage and production reg/sreg
pushing out new schema, and restarting dev/stage ldap with it. NOTE: restart slaves first to avoid replication issues.
new schema, ACLs, and server-core package pushed to stage. email sent to QA.
Notable bugs verified. Smoketest of AP turn up bug 667436 - request quota increase on stage gets escaped dino message
check that bug 664736 (dyslexia strikes again)
Summary: Deploy server-core rpm-1.7 to stage and production reg/sreg → Deploy server-core rpm-1.7 to stage and production reg/sreg and ap
New error found means that rpm version to push is now rpm-1.7-2
To clarify: reg/sreg have been tested and QA passed using python26-services-1.7-1 ap has been tested and QA passed using python26-services-1.7-2, which contains a bonus utf8 fix for a previously undiscovered issue that affects production account portal (bug 664736). The fix in 1.7-2 should be of no relevance to reg/sreg, so if it is desirable to upgrade reg/sreg to match ap for whatever reasons, coordinate an extra smoke test with QA after upgrading.
1.7-2 pushed to reg/sreg, also. Handing back to QA for reg/sreg smoketest just to be sure.
Pushed to production (along with ldap master failover for ldap structure cleanup).
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Verified on production 20110620
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.