{"action":"created","issue":{"url":"https://api.github.com/repos/habitat-sh/habitat/issues/5734","repository_url":"https://api.github.com/repos/habitat-sh/habitat","labels_url":"https://api.github.com/repos/habitat-sh/habitat/issues/5734/labels{/name}","comments_url":"https://api.github.com/repos/habitat-sh/habitat/issues/5734/comments","events_url":"https://api.github.com/repos/habitat-sh/habitat/issues/5734/events","html_url":"https://github.com/habitat-sh/habitat/issues/5734","id":368801467,"node_id":"MDU6SXNzdWUzNjg4MDE0Njc=","number":5734,"title":"[supervisor]  Service update channel persists between services unload/load","user":{"login":"smacfarlane","id":36851,"node_id":"MDQ6VXNlcjM2ODUx","avatar_url":"https://avatars0.githubusercontent.com/u/36851?v=4","gravatar_id":"","url":"https://api.github.com/users/smacfarlane","html_url":"https://github.com/smacfarlane","followers_url":"https://api.github.com/users/smacfarlane/followers","following_url":"https://api.github.com/users/smacfarlane/following{/other_user}","gists_url":"https://api.github.com/users/smacfarlane/gists{/gist_id}","starred_url":"https://api.github.com/users/smacfarlane/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/smacfarlane/subscriptions","organizations_url":"https://api.github.com/users/smacfarlane/orgs","repos_url":"https://api.github.com/users/smacfarlane/repos","events_url":"https://api.github.com/users/smacfarlane/events{/privacy}","received_events_url":"https://api.github.com/users/smacfarlane/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-10-10T18:46:57Z","updated_at":"2018-10-10T19:04:08Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"When changing the update channel for a service via `hab svc unload/load `,  the initial channel used persists until the supervisor is restarted.  This behavior is a little difficult to explain, so the reproduction steps are listed below.\r\n\r\n######\r\nBuild a package twice and upload both:\r\n\r\n```\r\nsmacfarlane/redis/4.0.10/20181010173224\r\nsmacfarlane/redis/4.0.10/20181010173335\r\n```\r\n\r\nPromote the older of the two packages to a channel;  \r\n\r\n```\r\nhab pkg promote smacfarlane/redis/4.0.10/20181010173224 foo\r\n```\r\n\r\nStart the supervisor and load the package with an at-once update strategy watching channel foo.\r\n\r\n```\r\nsup-run  # Studio environment\r\nhab svc load smacfarlane/redis --channel foo --strategy at-once\r\n```\r\n\r\nThe `20181010173224` version of the service is loaded as expected. \r\n\r\nUnload the service and load it again from the unstable channel. \r\n\r\n```\r\nhab svc unload smacfarlane/redis\r\nhab svc load smacfarlane/redis --channel unstable --strategy at-once\r\n```\r\n\r\nThe expected behavior would be that the `20181010173335` version would be installed and loaded as it is in the unstable channel and newer. \r\n\r\nStop the supervisor\r\n\r\n```\r\nhab sup term\r\n```\r\n\r\nStart the supervisor. Package should immediately update. \r\n\r\n```\r\nsup-run\r\nsup-log\r\n```\r\n\r\n\r\nI've tested this with Habitat 0.65.0 and 0.59.0 in a Linux studio.  There are also reports of this behavior with 0.65 on Windows.\r\n"},"comment":{"url":"https://api.github.com/repos/habitat-sh/habitat/issues/comments/428693414","html_url":"https://github.com/habitat-sh/habitat/issues/5734#issuecomment-428693414","issue_url":"https://api.github.com/repos/habitat-sh/habitat/issues/5734","id":428693414,"node_id":"MDEyOklzc3VlQ29tbWVudDQyODY5MzQxNA==","user":{"login":"mikemol","id":13550,"node_id":"MDQ6VXNlcjEzNTUw","avatar_url":"https://avatars2.githubusercontent.com/u/13550?v=4","gravatar_id":"","url":"https://api.github.com/users/mikemol","html_url":"https://github.com/mikemol","followers_url":"https://api.github.com/users/mikemol/followers","following_url":"https://api.github.com/users/mikemol/following{/other_user}","gists_url":"https://api.github.com/users/mikemol/gists{/gist_id}","starred_url":"https://api.github.com/users/mikemol/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mikemol/subscriptions","organizations_url":"https://api.github.com/users/mikemol/orgs","repos_url":"https://api.github.com/users/mikemol/repos","events_url":"https://api.github.com/users/mikemol/events{/privacy}","received_events_url":"https://api.github.com/users/mikemol/received_events","type":"User","site_admin":false},"created_at":"2018-10-10T19:04:08Z","updated_at":"2018-10-10T19:04:08Z","author_association":"NONE","body":"Fun! So this impacts Windows and Linux.\r\n\r\nTwo questions/clarifications:\r\n\r\n1. Does running `hab sup term` stop the services being run by the supervisor? Does it trigger lifecycle hooks?\r\n\r\n2. What version of the supervisor first introduced this problem?"}}
{"actor":{"display_login":"mikemol"}}