{"push_id":1183622332,"size":7,"distinct_size":7,"ref":"refs/heads/master","head":"3228a51f0b78d58ac605349ca8bf6145a26a2137","before":"61a9358dbd214aec9f500a2bf791e3e088dd484a","commits":[{"sha":"6de83d58537f576103d1f341e8da22fa9080b78a","author":{"name":"Girish Kalele","email":"f064f272e8452b925d8f88052a11a00cd2ed9436@google.com"},"message":"Update Godeps for github.com/skynetservices/skydns and github.com/miekg/dns","distinct":true,"url":"https://api.github.com/repos/jfrazelle/kubernetes/commits/6de83d58537f576103d1f341e8da22fa9080b78a"},{"sha":"65180ea25a4594c794dc14c47193559f9fb27dae","author":{"name":"Christian Simon","email":"3a69a7dd305e9c7705028afae27095688d25197a@swine.de"},"message":"Fix problems with container restarts and flocker\n\n* Removes meta dir, which prevents to detection of the correct mount\n  path\n\n* Fixes #22436","distinct":true,"url":"https://api.github.com/repos/jfrazelle/kubernetes/commits/65180ea25a4594c794dc14c47193559f9fb27dae"},{"sha":"8614be3c714ddeafe4698b88ad2870d1a27af3ec","author":{"name":"Girish Kalele","email":"f064f272e8452b925d8f88052a11a00cd2ed9436@google.com"},"message":"Bump kubedns version to 1.6 with latest skynetservices/skydns code\n\nBuilt kube-dns for all architectures and pushed containers to gcr.io","distinct":true,"url":"https://api.github.com/repos/jfrazelle/kubernetes/commits/8614be3c714ddeafe4698b88ad2870d1a27af3ec"},{"sha":"c3e9485dfa0eead690a1dfe33291ee55a0f54b66","author":{"name":"k8s-merge-robot","email":"90609b3a0723d5b4f9968c7035bcd6629ebfd177@gmail.com"},"message":"Merge pull request #28247 from girishkalele/skydns_godep_up\n\nAutomatic merge from submit-queue\n\nBump skydns godeps to latest\n\nUpdate Godeps for github.com/skynetservices/skydns and miekg/dns.\r\n\r\nBump kubedns version to 1.6 with latest skynetservices/skydns code\r\n    \r\nBuilt kube-dns for all architectures and pushed containers to gcr.io.","distinct":true,"url":"https://api.github.com/repos/jfrazelle/kubernetes/commits/c3e9485dfa0eead690a1dfe33291ee55a0f54b66"},{"sha":"821e6ec2a72b8453813923ac71d1c54f8aef91a8","author":{"name":"Jeff Grafton","email":"37780e769b84e50aeec1ef2668f6dba1732f01bc@google.com"},"message":"Make node e2e exit nonzero on test failures","distinct":true,"url":"https://api.github.com/repos/jfrazelle/kubernetes/commits/821e6ec2a72b8453813923ac71d1c54f8aef91a8"},{"sha":"b1b51a6fefada3e2a4167c1fd7bc986b6608b267","author":{"name":"k8s-merge-robot","email":"90609b3a0723d5b4f9968c7035bcd6629ebfd177@gmail.com"},"message":"Merge pull request #25873 from simonswine/fix-flocker-restart-master\n\nAutomatic merge from submit-queue\n\nFix problems with container restarts and flocker volumes\n\n[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/.github/PULL_REQUEST_TEMPLATE.md?pixel)]()\r\n\r\nThe issue is described in #22436. A pod with a flocker volume attached can't be restarted. A complete new pod has to be created, then everything is working fine.\r\n\r\nThe problem is around the `isReady` check. This ready state is not getting cleaned up for restarting containers. IMHO we don't need this ready state stored at all. Maybe it was meant to not call the flocker API during pod restarts, but I would rather have it removed... (happy about some hints why we need this lines)\r\n\r\nI tested it in a AWS/flocker cluster: starting/restarting/rescheduling on another node (in the same zone) works perfectly fine.","distinct":true,"url":"https://api.github.com/repos/jfrazelle/kubernetes/commits/b1b51a6fefada3e2a4167c1fd7bc986b6608b267"},{"sha":"3228a51f0b78d58ac605349ca8bf6145a26a2137","author":{"name":"Daniel Smith","email":"944ade84ac11352b3dc8101d650a2b977d92351c@google.com"},"message":"Merge pull request #28303 from ixdy/make-node-e2e-fail\n\nMake node e2e exit nonzero on test failures","distinct":true,"url":"https://api.github.com/repos/jfrazelle/kubernetes/commits/3228a51f0b78d58ac605349ca8bf6145a26a2137"}]}
{"actor":{"display_login":"jfrazelle"}}