recently we have upgraded Octopus from V4.1.8 to V2018.3.12. After upgrade, we are not seeing
Task History
Deployment History in the release
Deployment activity logs in the Audit.
Please see the screenshots for more information. Please revert back to me as soon as possible, this is kind of an urgent thing, since we are unable to derive who is deploying releases and causing issues while debugging issues.
Please note that this is not a permissions issue, because I’m an Octopus admin, have full access.
3. Deployment activity logs in the Audit.
Is this when you go to Configuration->Audit and filter the events by the Analysis_REVISE_WebApp project?
I’ve not been able to replicate the issue you are seeing locally, so could you go to Configuration->Test Permissions select yourself and click the Export button and send that CSV file through to me please, this should help me troubleshoot this issue.
Hi! Any progress with this problem? We are having similar issues after upgrading to 2018.4.5. We can see the Task History for some of our projects but not for all. At the moment we have not been able to reproduce this behaviour.
As I was unable to reproduce the issue locally, I am not sure why this issue is happening.
What version did you upgrade from?
Could you run the below SQL queries and let me know if any of them are returning any results.
SELECT *
FROM [dbo].[Event]
WHERE [ReleaseId] = '<ReleaseIdForWhichYouCannotSeeDeploymentHistory>'
SELECT *
FROM [dbo].[Event]
WHERE [TaskId] = '<ServerTaskIdForWhichYouCannotSeeDeploymentHistory>'
in my case, because of Active Directory group permissions, i wasn’t able to see task history, audit, deployment history. I had to remove Active Directory group to access the history.
My account is a member of Octopus Administrators via an AD group. This AD group is in turn a member of another AD group which we use to give Performance testers access in Octopus.
For some reason which I don’t understand this introduces restrictions to what my account can see in Octopus.
If I use another account and include it only in Octopus Administrators it seems to work fine so problem solved.
Thanks Joacim for the extra information, I’ll go through the changes we’ve made between the versions your upgraded and see if I can find out the reason that is causing this issue. I know we’ve done a fair bit of work in the permissions space.
Apologies for the long turn around time on this bug. It was attached to a larger piece of work that was intended to resolve it. For those who were curious it was likely introduced in either 2018.3.6 or 2018.3.10 - there were other manifestations of this bug.
