Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Old execution history hidden after running pipelines in >= 1.8.x #3256
Old (<= 1.7.x) execution history hidden after running pipelines in >= 1.8.x
Distributed Spinnaker (V1) deployment into GKE
Orca / Execution history
After upgrading from 1.7.4 to 1.8.5, execution history is present. Immediately after starting a pipeline post upgrade, old execution history for that pipeline no longer shows up. Old executions are still present - can access directly via the API if you know the ID, or if you filter on statuses which don't have a 1.8.x execution yet. Seen in UI, verification in API per additional details below.
Not a huge deal for us, but didn't see anything in the changelog or issues, curious if this is expected, if others are seeing the same. Verified same behavior after upgrading to 1.9.0 (though via 1.8.5 - have not tried 1.7.x -> 1.9.0 directly).
changed the title
<= 1.7.x execution history hidden after running pipelines in >= 1.8.x
Aug 27, 2018
I tried this quickly myself---I started a 1.7.4 Spinnaker, ran some pipelines, upgraded to 1.8.5, and was still able to see the prior executions (even after doing some executions in 1.8.5). So there's obviously some set of conditions under which this bug happens, but I didn't hit that case in my testing.
no errors in the chrome console when loading an affected #/applications/<app>/executions page.
after @ezimanyi's comment (thanks for testing!), i also set up a clean spinnaker instance and as he found, did keep execution history after the upgrade. i'll try to compare settings, old and new execution records, etc between the affected and working spinnaker instances this morning.
fwiw, i'm seeing this on two dev spinnaker instances that should have the same configuration a prod instance, but have less activity.
I know this issue has been closed. but may I ask how to retrieve the execution history more than 14 days in this situation?
I used the API and got the same result from the UI that the history more than 14 days older than the latest one cannot be retrieved. but if I deleted my latest execution, the old pipelines (over 14 days) were back again from both UI and API.
Pretty sure you're running into this: https://github.com/spinnaker/orca/blob/master/orca-web/src/main/groovy/com/netflix/spinnaker/orca/controllers/TaskController.groovy#L554