{"action":"created","issue":{"url":"https://api.github.com/repos/openshift/origin/issues/6209","repository_url":"https://api.github.com/repos/openshift/origin","labels_url":"https://api.github.com/repos/openshift/origin/issues/6209/labels{/name}","comments_url":"https://api.github.com/repos/openshift/origin/issues/6209/comments","events_url":"https://api.github.com/repos/openshift/origin/issues/6209/events","html_url":"https://github.com/openshift/origin/pull/6209","id":120511947,"number":6209,"title":"Prevent dev cluster deploy from using stale config","user":{"login":"marun","id":451477,"avatar_url":"https://avatars.githubusercontent.com/u/451477?v=3","gravatar_id":"","url":"https://api.github.com/users/marun","html_url":"https://github.com/marun","followers_url":"https://api.github.com/users/marun/followers","following_url":"https://api.github.com/users/marun/following{/other_user}","gists_url":"https://api.github.com/users/marun/gists{/gist_id}","starred_url":"https://api.github.com/users/marun/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/marun/subscriptions","organizations_url":"https://api.github.com/users/marun/orgs","repos_url":"https://api.github.com/users/marun/repos","events_url":"https://api.github.com/users/marun/events{/privacy}","received_events_url":"https://api.github.com/users/marun/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":12,"created_at":"2015-12-05T00:08:44Z","updated_at":"2016-02-11T19:15:13Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/openshift/origin/pulls/6209","html_url":"https://github.com/openshift/origin/pull/6209","diff_url":"https://github.com/openshift/origin/pull/6209.diff","patch_url":"https://github.com/openshift/origin/pull/6209.patch"},"body":"When a dev cluster is deployed with vagrant, the nodes wait for their\r\nconfiguration to be created.  If stale configuration is already present,\r\nthey may use that configuration before the master has a chance to\r\ngenerate new configuration.  This change marks existing configuration as\r\nstale at the beginning of provisioning to avoid that possiblity."},"comment":{"url":"https://api.github.com/repos/openshift/origin/issues/comments/183015857","html_url":"https://github.com/openshift/origin/pull/6209#issuecomment-183015857","issue_url":"https://api.github.com/repos/openshift/origin/issues/6209","id":183015857,"user":{"login":"marun","id":451477,"avatar_url":"https://avatars.githubusercontent.com/u/451477?v=3","gravatar_id":"","url":"https://api.github.com/users/marun","html_url":"https://github.com/marun","followers_url":"https://api.github.com/users/marun/followers","following_url":"https://api.github.com/users/marun/following{/other_user}","gists_url":"https://api.github.com/users/marun/gists{/gist_id}","starred_url":"https://api.github.com/users/marun/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/marun/subscriptions","organizations_url":"https://api.github.com/users/marun/orgs","repos_url":"https://api.github.com/users/marun/repos","events_url":"https://api.github.com/users/marun/events{/privacy}","received_events_url":"https://api.github.com/users/marun/received_events","type":"User","site_admin":false},"created_at":"2016-02-11T19:15:12Z","updated_at":"2016-02-11T19:15:12Z","body":"@danmcp The marker file is intended to prevent nodes from provisioning until the master has the chance to regenerate configuration.  The only alternative I can think of would be the reverse - Vagrantfile removes the marker, master adds the marker after config generation/regeneration, and nodes wait on the existence of the marker.  I'm not sure that's any simpler though."}}