Comment on Some bad code just broke a billion Windows machines
Joelk111@lemmy.world 1 month agoYeah, our VMs completely died at work. Has to set up temporary stuff on hardware we had laying around today. Was kinda fun, but stressful haha.
Comment on Some bad code just broke a billion Windows machines
Joelk111@lemmy.world 1 month agoYeah, our VMs completely died at work. Has to set up temporary stuff on hardware we had laying around today. Was kinda fun, but stressful haha.
dan@upvote.au 1 month ago
Could you just revert VMs to a snapshot before the update? Or do you not take periodic snapshots? You could probably also mount the VM’s drive on the host and delete the relevant file that way.
EncryptKeeper@lemmy.world 1 month ago
Yes you can just go into safe mode on an affected machine and delete the offending file. The problem is it took a couple hours before that resolution was found, and it has to be done by hand on every VM. I can’t just run an Ansible playbook against hundreds of non-booted VMs. Then you have to consider in the case of servers, there might be a specific start up order, certain things might have to be started before other things and further fixing might be required given that every VM hard crashed. At the minimum it took many companies 6-12 hours to get back up and running and on many more it could take days.
dan@upvote.au 1 month ago
Makes sense - thanks for the details.
Joelk111@lemmy.world 1 month ago
Yeah, like the other person said, corporate IT is responsible for that stuff.
UnsavoryMollusk@lemmy.world 1 month ago
This is assuming you have those access. Some companies can sometimes be a bit … Stupid.