256,338 rows affected.
I can do one better. Novo Nordisk lost their Canadian patent for Ozempic because someone forgot to fill out the renewal with a $400 admin fee.
They will lose $10B before patent ending.
But they saved $400. Someone needs to talk to HR.
“Ah, shit. Oh well. They have backups.”
“…”
“They have backups, right?”
If they don’t, that’s something you can’t blame on a new start.
Reminds me of a major incident I got involved in. I was the Problem Manager and not MIM (Major Incident Management), but I’ve had years of MIM experience so was asked to help out on this one. The customer manufactured blood plasma and each of the lots on the production floor was worth a cool $1 million. The application that was down and had brought production down was not the app that actually handled production, but an application (service) that supplied data to it.
Of course the customer thought that app was not Mission Critical so it didn’t have redundancy. I joined the call and first thing I asked was when did the last change go through on this app… Spoiler: I had the change in front of me and it went in the previous night. The admin of the app speaks up that he did a change the previous night… And NO the MIM team had NOT looked at that change yet… Did I mention this was FOUR FUCKING HOURS into the outage? That is MIM 101. Something goes down, look to see who last fucked with it.
This is why you need experienced MIM people in enterprise environments.
So I took control of the MIM, instructed the App Admin to share his screen and walk us through the change he did the previous night… Two screens in and OH… Look at that… There’s a check box that put the app into read only (or something like that, this happened back in 2009 and I don’t remember all the details). I’d never seen the application before in my life, but knew that check box being checked, just based on the verbiage, could not be right… So I asked… The Admin, sounding embarrassed, said yeah he forgot to uncheck that box last night…
Fuck me.
He unchecked the box, bounced the app and what do you know… It started to work.
A single damn check box brought down the production line of a multi-billion dollar company.
My investigation for that Problem was a bit scathing to multiple levels of the customer. If a service supports a Tier 1 production app and that Tier 1 app would stop working if that service goes down… GUESS WHAT! That service is MISSION FUCKING CRITICAL and it should be supported as such. My employer was not on the hook for this one, as both applications involved were customer supported.
I would love to say that the above is an uncommon occurrence, but honestly it is the main reason for outages in my experience. Something small and stupid that is easily missed.
What’s with the weird vertical artifacts in this image?
this meme is made out of corduroy
Trying to hide the slop
Scanlines in tate mode.
I was hired as a backup representative and just wanted to know what I was dealing with and make a clear statement.
…which would make it about 99,9999999% their fault for giving a new employee write access to the DB.
The data was a mess and needed to be cleaned up anyway.
Oh, so that’s what the Delete button does.
Have you tried turning it off and on again?
All of my bananas are worthless now!
Right click Recycle Bin --> Restore
If you have the ability to do this on your first day, it’s 100% not your fault.
This is literally true and I know it because I came here to say it and then noticed you beat me by 5 minutes.
This is literally true and I know it because I came here to say it and then noticed you beat me by 21 hours.
This is literally true and I know it because these three people said so
It’s fine, just restore the backup.
The what now?
It’s right there, in the room with the unicorns and leprechauns.
Right next to the windows backup cd
You know how we installed that system and have been waiting for a chance to see how it works
You go ask the other monkey who was in charge of the backup … and all they do is incoherently scream at you.
Backup straight out the building. Ain’t about to be there when they find out.
Every seasoned IT person, devOps or otherwise has accidentally made a catastrophic mistake. I ask that in interviews :D
Not IT but data analyst. Missed a 2% salary increase for our union members when projecting next year’s budget. $12 million mistake that was only caught once it was too late to fix.
I once deleted the whole production kubernetes environment trying to fix an update to prod give awry, at11pm. My saving grace was that our systems are barely used between 10pm-8am, and I managed to teach myself by reading enough docs and stack overflow comments to rebuild it and fix the initial mistake before 5am. Never learned how to correctly use a piece of stack that quickly before or since.
Nothing focuses the mind more than the panicked realisation that you have just hosed the production systems
I deleted all of our DNS records. As it turns out, you can’t make money when you can’t resolve dns records :P
Mine was replacing a failed hard drive in array.
- Check array health, see one failed member
- popped out the hot swappable old drive , popped in the new one
- Check array health to make sure the array rebuild is underway
- See array now has TWO failed member, and realize I feel the drive in my hand still spinning down
shit.
I accidentally rm’ed /bin on a remote host located in another country, and had to wait for someone to get in and fix it.
I pushed a $1 bln test trade through production instead of my test environment… that was a sweaty 30 minutes
Yep. Ran a config as code migration on prod instead of dev. We introduced new safeguards for running against prod after that. And changed the expectations for primary on call to do dev work with down time. Shifted to improving ops tooling or making pretty charts from all the metrics. Actually ended up reducing toil substantially over the next couple quarters.
10/10 will absolutely still do something dumb again.
