{"action":"created","issue":{"url":"https://api.github.com/repos/Azure/service-fabric-issues/issues/940","repository_url":"https://api.github.com/repos/Azure/service-fabric-issues","labels_url":"https://api.github.com/repos/Azure/service-fabric-issues/issues/940/labels{/name}","comments_url":"https://api.github.com/repos/Azure/service-fabric-issues/issues/940/comments","events_url":"https://api.github.com/repos/Azure/service-fabric-issues/issues/940/events","html_url":"https://github.com/Azure/service-fabric-issues/issues/940","id":308078524,"number":940,"title":"[AzureChinaCloud] : ServiceFabric RepairManager Service not available after Cluster Upgrade","user":{"login":"rajaprad","id":13054214,"avatar_url":"https://avatars3.githubusercontent.com/u/13054214?v=4","gravatar_id":"","url":"https://api.github.com/users/rajaprad","html_url":"https://github.com/rajaprad","followers_url":"https://api.github.com/users/rajaprad/followers","following_url":"https://api.github.com/users/rajaprad/following{/other_user}","gists_url":"https://api.github.com/users/rajaprad/gists{/gist_id}","starred_url":"https://api.github.com/users/rajaprad/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rajaprad/subscriptions","organizations_url":"https://api.github.com/users/rajaprad/orgs","repos_url":"https://api.github.com/users/rajaprad/repos","events_url":"https://api.github.com/users/rajaprad/events{/privacy}","received_events_url":"https://api.github.com/users/rajaprad/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":{"login":"vaishnavk","id":11414395,"avatar_url":"https://avatars1.githubusercontent.com/u/11414395?v=4","gravatar_id":"","url":"https://api.github.com/users/vaishnavk","html_url":"https://github.com/vaishnavk","followers_url":"https://api.github.com/users/vaishnavk/followers","following_url":"https://api.github.com/users/vaishnavk/following{/other_user}","gists_url":"https://api.github.com/users/vaishnavk/gists{/gist_id}","starred_url":"https://api.github.com/users/vaishnavk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vaishnavk/subscriptions","organizations_url":"https://api.github.com/users/vaishnavk/orgs","repos_url":"https://api.github.com/users/vaishnavk/repos","events_url":"https://api.github.com/users/vaishnavk/events{/privacy}","received_events_url":"https://api.github.com/users/vaishnavk/received_events","type":"User","site_admin":false},"assignees":[{"login":"vaishnavk","id":11414395,"avatar_url":"https://avatars1.githubusercontent.com/u/11414395?v=4","gravatar_id":"","url":"https://api.github.com/users/vaishnavk","html_url":"https://github.com/vaishnavk","followers_url":"https://api.github.com/users/vaishnavk/followers","following_url":"https://api.github.com/users/vaishnavk/following{/other_user}","gists_url":"https://api.github.com/users/vaishnavk/gists{/gist_id}","starred_url":"https://api.github.com/users/vaishnavk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vaishnavk/subscriptions","organizations_url":"https://api.github.com/users/vaishnavk/orgs","repos_url":"https://api.github.com/users/vaishnavk/repos","events_url":"https://api.github.com/users/vaishnavk/events{/privacy}","received_events_url":"https://api.github.com/users/vaishnavk/received_events","type":"User","site_admin":false}],"milestone":null,"comments":2,"created_at":"2018-03-23T15:38:50Z","updated_at":"2018-03-28T18:55:56Z","closed_at":null,"author_association":"NONE","body":"Resource ID: /subscriptions/<HIDDEN>/resourcegroups/<HIDDEN>/providers/Microsoft.ServiceFabric/clusters/<HIDDEN>\r\nPatch Orchestration Cluster changes are done as listed in the documentation here: **https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-patch-orchestration-application**\r\nHowever after the upgrade - we are not able to see RepairManagerService under system services.\r\n\r\nThere is a Support ticket open with Azure China : SR_2018031423149_[HMC]RepairManager Service unavailable after upgrade\r\nService Request SR2018031423149\r\n\r\n**Updates from the ticket:**\r\n\r\n发件人: HIDDEN\r\n发送时间: Wednesday, March 14, 2018 9:50 PM\r\n收件人: HIDDEN\r\n抄送: HIDDEN\r\n主题: RE: SR_2018031423149_[HMC]RepairManager Service unavailable after upgrade\r\n\r\n\r\nI checked all Primary Nodes, and none of it has FabricRM Process running. \r\nNote: The cluster upgrade with RepairManager changes were done Sunday, so there is already past the two days wait period.\r\n\r\n![fabricrmunavailable](https://user-images.githubusercontent.com/13054214/37832588-69bc61ea-2e7f-11e8-9d54-aebe817019d2.png)\r\n\r\n\r\nThanks,\r\nPradebban Raja\r\n\r\nFrom: HIDDEN\r\nSent: Wednesday, March 14, 2018 2:07 AM\r\nTo: HIDDEN\r\nCc: HIDDEN\r\nSubject: 答复: SR_2018031423149_[HMC]RepairManager Service unavailable after upgrade\r\n\r\nDear customer,\r\n\r\nWe checked this service fabric’s configure in backend and confirmed with ms engineer, if you create a service fabric with Repair Manager Service, it will be has a repair system service in Explorer.\r\nBut if you add a Repair Manager Service in an exsit service fabric, There may  be one or two days of delay to show this repair system service in Explorer. But we can use below method to check repair system service is run normal in Service Fabric.\r\nCheck Method:\r\nPlease RDP to the  node of your service fabric, and check if the RepairManager is run in task management. \r\n\r\n![supportcheck](https://user-images.githubusercontent.com/13054214/37838473-5f32fb30-2e8e-11e8-8a8a-20367ccdb2cb.png)\r\n\r\nNotes:\r\nThis process only run in one node of your service fabric, so please check all your nodes in this service fabric to foud this process.\r\n \r\n\r\n \r\n"},"comment":{"url":"https://api.github.com/repos/Azure/service-fabric-issues/issues/comments/376997579","html_url":"https://github.com/Azure/service-fabric-issues/issues/940#issuecomment-376997579","issue_url":"https://api.github.com/repos/Azure/service-fabric-issues/issues/940","id":376997579,"user":{"login":"rajaprad","id":13054214,"avatar_url":"https://avatars3.githubusercontent.com/u/13054214?v=4","gravatar_id":"","url":"https://api.github.com/users/rajaprad","html_url":"https://github.com/rajaprad","followers_url":"https://api.github.com/users/rajaprad/followers","following_url":"https://api.github.com/users/rajaprad/following{/other_user}","gists_url":"https://api.github.com/users/rajaprad/gists{/gist_id}","starred_url":"https://api.github.com/users/rajaprad/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rajaprad/subscriptions","organizations_url":"https://api.github.com/users/rajaprad/orgs","repos_url":"https://api.github.com/users/rajaprad/repos","events_url":"https://api.github.com/users/rajaprad/events{/privacy}","received_events_url":"https://api.github.com/users/rajaprad/received_events","type":"User","site_admin":false},"created_at":"2018-03-28T18:55:56Z","updated_at":"2018-03-28T18:55:56Z","author_association":"NONE","body":"@vaishnavk - Sanity checks are already done as mentioned in the link."}}
{"actor":{"display_login":"rajaprad"}}