{"action":"created","issue":{"url":"https://api.github.com/repos/Azure/acs-engine/issues/3533","repository_url":"https://api.github.com/repos/Azure/acs-engine","labels_url":"https://api.github.com/repos/Azure/acs-engine/issues/3533/labels{/name}","comments_url":"https://api.github.com/repos/Azure/acs-engine/issues/3533/comments","events_url":"https://api.github.com/repos/Azure/acs-engine/issues/3533/events","html_url":"https://github.com/Azure/acs-engine/issues/3533","id":343888954,"node_id":"MDU6SXNzdWUzNDM4ODg5NTQ=","number":3533,"title":"Can not scale up using acs-engine ","user":{"login":"gdbgit","id":9956650,"node_id":"MDQ6VXNlcjk5NTY2NTA=","avatar_url":"https://avatars1.githubusercontent.com/u/9956650?v=4","gravatar_id":"","url":"https://api.github.com/users/gdbgit","html_url":"https://github.com/gdbgit","followers_url":"https://api.github.com/users/gdbgit/followers","following_url":"https://api.github.com/users/gdbgit/following{/other_user}","gists_url":"https://api.github.com/users/gdbgit/gists{/gist_id}","starred_url":"https://api.github.com/users/gdbgit/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gdbgit/subscriptions","organizations_url":"https://api.github.com/users/gdbgit/orgs","repos_url":"https://api.github.com/users/gdbgit/repos","events_url":"https://api.github.com/users/gdbgit/events{/privacy}","received_events_url":"https://api.github.com/users/gdbgit/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2018-07-24T05:24:41Z","updated_at":"2018-08-01T14:29:17Z","closed_at":null,"author_association":"NONE","body":"<!-- Thanks for filing an issue! Before hitting the button, please answer these questions. It's helpful to search the existing GitHub issues first. It's likely that another user has already reported the issue you're facing, or it's a known issue that we're already aware of-->\r\n\r\n**Is this a request for help?**:\r\n\r\n---Yes\r\n\r\n**Is this an ISSUE or FEATURE REQUEST?** (choose one):\r\n\r\n---ISSUE\r\n\r\n**What version of acs-engine?**:\r\n\r\n---Version: v0.19.1\r\nGitCommit: f50fe5fe\r\nGitTreeState: clean\r\n\r\n\r\n<!--\r\nIf this is a ISSUE, please:\r\n  - Fill in as much of the template below as you can.  If you leave out\r\n    information, we can't help you as well.\r\n\r\nIf this is a FEATURE REQUEST, please:\r\n  - Describe *in detail* the feature/behavior/change you'd like to see.\r\n\r\nIn both cases, be ready for followup questions, and please respond in a timely\r\nmanner.  If we can't reproduce a bug or think a feature already exists, we\r\nmight close your issue.  If we're wrong, PLEASE feel free to reopen it and\r\nexplain why.\r\n-->\r\n\r\n**Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)**\r\nKubernetes,\r\n\r\n Version: v1.8.3\r\nGit commit:\r\nec1d7de4456e6a397c7f931f0a2bfc74a6ca2e9c \r\n\r\n**What happened**:\r\nWhen scale up to 17 nodes, the VMs didn’t provision successfully due to some issues at CRP end and the deployment aborted. The extension deployment didn’t start which cause kubelet related service didn’t get installed properly on agent nodes. When scaled down, the script will return error ‘cannot find node-xx’. Could you please help let us know how to mitigate this?\r\nReference case: 118072418639291\r\nReference engineer: shuanglu\r\n\r\n**What you expected to happen**:\r\nscale successful\r\n\r\n**How to reproduce it** (as minimally and precisely as possible):\r\nassign var then run command:\r\nacs-engine scale \\\r\n    --subscription-id $SUBSCRIPTION_ID \\\r\n    --resource-group $RESOURCE_GROUP \\\r\n    --location $LOCATION \\\r\n    --deployment-dir $DEPLOYMENT_DIR \\\r\n    --new-node-count $NEW_NODE_COUNT \\\r\n    --node-pool $NODE_POOL \\\r\n    --master-FQDN $FQDN\r\n\r\n**Anything else we need to know**:\r\nNothing"},"comment":{"url":"https://api.github.com/repos/Azure/acs-engine/issues/comments/409594916","html_url":"https://github.com/Azure/acs-engine/issues/3533#issuecomment-409594916","issue_url":"https://api.github.com/repos/Azure/acs-engine/issues/3533","id":409594916,"node_id":"MDEyOklzc3VlQ29tbWVudDQwOTU5NDkxNg==","user":{"login":"Shuanglu","id":6046716,"node_id":"MDQ6VXNlcjYwNDY3MTY=","avatar_url":"https://avatars0.githubusercontent.com/u/6046716?v=4","gravatar_id":"","url":"https://api.github.com/users/Shuanglu","html_url":"https://github.com/Shuanglu","followers_url":"https://api.github.com/users/Shuanglu/followers","following_url":"https://api.github.com/users/Shuanglu/following{/other_user}","gists_url":"https://api.github.com/users/Shuanglu/gists{/gist_id}","starred_url":"https://api.github.com/users/Shuanglu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Shuanglu/subscriptions","organizations_url":"https://api.github.com/users/Shuanglu/orgs","repos_url":"https://api.github.com/users/Shuanglu/repos","events_url":"https://api.github.com/users/Shuanglu/events{/privacy}","received_events_url":"https://api.github.com/users/Shuanglu/received_events","type":"User","site_admin":false},"created_at":"2018-08-01T14:29:17Z","updated_at":"2018-08-01T14:29:17Z","author_association":"NONE","body":"@jackfrancis I tried to reproduce the issue recently. I guess the node count was recorded in somewhere. When the 1st scale up operation failed, it created the node VM and node count was increased but  due to cse didn't get executed, the data in k8s didn't change. This makes the following operation like scale down will fail to cordon the failed node and scale up will ignore the failed node. Any idea how to mitigate this?"}}
{"actor":{"display_login":"Shuanglu"}}