jpappa200 opened a new issue, #7590: URL: https://github.com/apache/trafficcontrol/issues/7590
<!-- ************ STOP!! ************ If this issue identifies a security vulnerability, DO NOT submit it! Instead, contact the Apache Traffic Control Security Team at [email protected] and follow the guidelines at https://apache.org/security regarding vulnerability disclosure. - For *SUPPORT QUESTIONS*, use the #traffic-control channel on the ASF slack (https://s.apache.org/tc-slack-request) or the Traffic Control Users mailing list (send an email to [email protected] to subscribe). - Before submitting, please **SEARCH GITHUB** for a similar issue or PR * https://github.com/apache/trafficcontrol/issues * https://github.com/apache/trafficcontrol/pulls --> <!-- Do not submit security vulnerabilities or support requests here - see above --> ## This Bug Report affects these Traffic Control components: <!-- delete all those that don't apply --> - Traffic Control Cache Config (`t3c`, formerly ORT) ## What did you do? <!-- If the current behavior is a bug, please provide the *STEPS TO REPRODUCE* and include the applicable TC version. --> When we update a cache to Rocky 8.8 the new version of git that is installed will enforce the permissions on the repo and throw the following error `fatal: detected dubious ownership in repository at '/opt/trafficserver/etc/trafficserver'` ## What did you expect to happen? <!-- Describe how the bug happens --> when t3c runs config file changes are committed to a git repo to maintain an history of changes. ## What actually happened? <!-- Describe what the behavior would be without the bug --> git now requires the owner of the git repo to be the same as the person committing to the repo. since t3c has to run as root and /opt/trafficserver/etc/trafficserver has to be owned by the ats user, t3c needs to look at the config to see if an exception exists, if not, it needs to be added to the global config. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
