3.5 had an issue with directory permissions

Legacy Uncategorised
1

When upgrading from 3.4.14 to 3.5 the service wouldn’t start until I made the user that the service was running under have full permissions to the c:\octopus directory, is that expected?

Thank You

2

Hi Leslie,

Thanks so much for getting in touch, and upgrading to Octopus 3.5 so quickly. I’m so sorry you’ve run into this bug. I’ve logged this GitHub Issue to fix it in 3.5.1: https://github.com/OctopusDeploy/Issues/issues/2890

Hope that helps!
Mike