Closed Bug 938394 Opened 12 years ago Closed 12 years ago

new persona stacks with yum-autoupdate exluding nodejs

Categories

(Cloud Services :: Operations: Miscellaneous, task)

Product:
Cloud Services
Component:
Operations: Miscellaneous
Platform:
x86_64
Linux
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: gene, Assigned: gene)

Details

https://github.com/mozilla/identity-ops/commit/2d4304e730e30c83a81112e28878884cb96a51e5 I'd like to switch to new production stacks that have this code change. Stacks are 1114
Assignee: server-ops → nobody
Component: Server Operations → Operations
Product: mozilla.org → Mozilla Services
QA Contact: shyam
Version: other → unspecified
Assignee: nobody → edwong
QA signs off on the new stacks. Green light on deploy.
Assignee: edwong → gene
DNS has been cutover 16:16
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Shoot. I built 1114 using the old AMIs. I noticed after going live that hosts were failing due to nodejs being updated. I reverted DNS back to stack 1028 and am building new stacks now using the correct AMIs
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
New stacks 1117 built and DNS has been pointed to them
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Creating staging stack 1118 now
Status: RESOLVED → REOPENED
QA Contact: kthiessen
Resolution: FIXED → ---
1118 has been built and DNS pointed to it. this stack has the same application version as the previous stage stack but has the new nodejs yum-autoupdate exclusion
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Old deployment -- belatedly marking VERIFIED.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.