Closed
Bug 664175
Opened 14 years ago
Closed 14 years ago
Deploy server-core rpm-1.7 to stage and production reg/sreg and ap
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: telliott, Assigned: petef)
Details
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
Assignee | ||
Comment 1•14 years ago
|
||
pushing out new schema, and restarting dev/stage ldap with it. NOTE: restart slaves first to avoid replication issues.
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → petef
Assignee | ||
Comment 2•14 years ago
|
||
new schema, ACLs, and server-core package pushed to stage. email sent to QA.
Comment 3•14 years ago
|
||
Notable bugs verified.
Smoketest of AP turn up bug 667436 - request quota increase on stage gets escaped dino message
Comment 4•14 years ago
|
||
check that bug 664736 (dyslexia strikes again)
Reporter | ||
Updated•14 years ago
|
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
Reporter | ||
Comment 5•14 years ago
|
||
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.
Assignee | ||
Comment 7•14 years ago
|
||
1.7-2 pushed to reg/sreg, also. Handing back to QA for reg/sreg smoketest just to be sure.
Assignee | ||
Comment 8•14 years ago
|
||
Pushed to production (along with ldap master failover for ldap structure cleanup).
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•