Username is not in the sudoers file.
This incident will be reported. https://twitter.com/kvlly/status/1297524702320250880
First month on the job in tech, I kept getting this error. And every time, I nervous sweat a little more.
Until finally, I couldn't take it anymore. I slunk to my would-be mentor's cubicle, and blurted out an apology, a confession & a question.
"WHO is this being reported to??"
He laughed.
Very, very hard.
"You. It's you, Jacquie. On your VM. No one else would have known"
I was learning how to use a "config management" tool called SaltStack.
The two seniors had many a conversation around it that sat in on, and once I lost it laughing because whenever they talked all I could picture was this but with env labels taped on their foreheads.
Anyway. I promise we're still on topic.
Knowing that only I would see the silly mistakes I was making really boosted my confidence. I felt UNSTOPPABLE.
Right up until the moment I sudo removed every user across my small vm cluster from the sudoers file.
I tried everything I could think of to fix the problem.
“Username is not in the sudoers file.
This incident will be reported”
I no longer feared the incident report, but I had not yet learned to use github or similar. I feared for the one version that had worked.
So I once again slunk over to his cubicle.
"Hi, I think I sudo'd away sudo...??"
"what"
"Like I might have used SaltStack to sudo away all the sudoers by accident. The internet told me it was best to not give everyone sudo"
Cue second bout of laughter and a "oh no, you'll need to remake the VMs"
"WHAT. I can't fix this??"
"not if no one can sudo"
FWIW I still sometimes shout SUPER USER DOOOOO while using sudo.
Anyway, I mourned my carefully crafted VMs and started over.
Imagine my excitement and frustration when MONTHS later, another dev introduced me to my first Source Code Management tool. 😂
You can follow @devopsjacquie.
Tip: mention @twtextapp on a Twitter thread with the keyword “unroll” to get a link to it.

Latest Threads Unrolled: