{"action":"closed","issue":{"url":"https://api.github.com/repos/projectkudu/kudu/issues/2952","repository_url":"https://api.github.com/repos/projectkudu/kudu","labels_url":"https://api.github.com/repos/projectkudu/kudu/issues/2952/labels{/name}","comments_url":"https://api.github.com/repos/projectkudu/kudu/issues/2952/comments","events_url":"https://api.github.com/repos/projectkudu/kudu/issues/2952/events","html_url":"https://github.com/projectkudu/kudu/issues/2952","id":423487444,"node_id":"MDU6SXNzdWU0MjM0ODc0NDQ=","number":2952,"title":"Web App service not restarting after zip deploy, previous site package serving requests/Loaded into memory","user":{"login":"jstallm","id":6054668,"node_id":"MDQ6VXNlcjYwNTQ2Njg=","avatar_url":"https://avatars3.githubusercontent.com/u/6054668?v=4","gravatar_id":"","url":"https://api.github.com/users/jstallm","html_url":"https://github.com/jstallm","followers_url":"https://api.github.com/users/jstallm/followers","following_url":"https://api.github.com/users/jstallm/following{/other_user}","gists_url":"https://api.github.com/users/jstallm/gists{/gist_id}","starred_url":"https://api.github.com/users/jstallm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jstallm/subscriptions","organizations_url":"https://api.github.com/users/jstallm/orgs","repos_url":"https://api.github.com/users/jstallm/repos","events_url":"https://api.github.com/users/jstallm/events{/privacy}","received_events_url":"https://api.github.com/users/jstallm/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":24,"created_at":"2019-03-20T21:46:34Z","updated_at":"2019-03-26T18:03:09Z","closed_at":"2019-03-26T18:03:08Z","author_association":"NONE","body":"I noticed today that upon successfully deploying my application from an Azure Devops release pipeline that after deployment, the previous artifact was serving responses to requests vs the latest deployed artifact UNTIL I restarted the application. This was very strange since I was under the impression that previous assemblies were unloaded after a deployment to an app service. \r\n\r\n### Repro steps.\r\n\r\nHere were steps for me to produce;\r\nDeploy app service using Azure Devops App Service Deploy task. Create a rest api endpoint on the application which simply returns the assembly version using a setter equal to \r\n\r\n`typeof(Program).Assembly.GetCustomAttribute<AssemblyInformationalVersionAttribute>().InformationalVersion`\r\nas a string.\r\nEven if the two artifacts have completely different versions, the assembly that is loaded into memory appears to still be version of application that was previously overridden during the deployment. Run a restart on the application using azure portal. Re-run a request to the endpoint that returns the assembly version and this time it will have the latest deployed version. \r\n\r\nHow is it that after a deployment the previous assembly is still loaded into memory such that a request to the app service returns a response from the application artifact that was JUST overriden with a new version? Why does restarting load the latest deployed artifact but not a deployment task in azure devops?\r\n\r\n@suwatch  could this be a bug from commit 8c8eba7?\r\n\r\nThis odd issue happened on both an api app and web app. Also happened on free and paid plan. "}}
{"actor":{"display_login":"jstallm"}}