4

At work I help manage a fleet of Apple hardware that acts as our iOS build pipeline, and today I tested out MacOS Sonoma on one of the build nodes. The update went fine, but the test build failed because it didn't have sudo access for a specific command. I looked into it a little more, and it appears that the update set the sudoers file back to default! Like, why would you do that? Why would you mess with a configuration like that just for an OS update? It doesn't make any sense to me, and now I'll have to go and fix each sudoers file manually after I update the rest of the nodes. So, thanks Apple.

Comments
  • 0
    use ansible
  • 2
    @vane it's not so much finding a way to fix the problem, it's more the principle. I'm more annoyed that Apple would decide it's ok to reset the sudoers file, like no one's system depends on it.
  • 0
    The update wanted to feel important :)
Add Comment