Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

e2e flake: "Syncing sources to container" failed in PR builder #34214

Closed
wojtek-t opened this issue Oct 6, 2016 · 6 comments · Fixed by #34257
Closed

e2e flake: "Syncing sources to container" failed in PR builder #34214

wojtek-t opened this issue Oct 6, 2016 · 6 comments · Fixed by #34257
Assignees
@jbeda
Labels
area/build-release area/test-infra kind/flake Categorizes issue or PR as related to a flaky test. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@wojtek-t
Copy link
Member

wojtek-t commented Oct 6, 2016 

+++ [1006 00:35:19] Syncing sources to container
rsync: safe_read failed to read 1 bytes [sender]: Connection reset by peer (104)
rsync error: error in rsync protocol data stream (code 12) at io.c(276) [sender=3.1.1]
Makefile:239: recipe for target 'release' failed
make: *** [release] Error 1
Build step 'Execute shell' marked build as failure

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/pr-logs/pull/34082/kubernetes-pull-build-test-e2e-gce/61951/

@kubernetes/test-infra-maintainers
@wojtek-t wojtek-t added priority/backlog Higher priority than priority/awaiting-more-evidence. area/test-infra kind/flake Categorizes issue or PR as related to a flaky test. labels Oct 6, 2016
@wojtek-t wojtek-t mentioned this issue Oct 6, 2016
Merged
@jszczepkowski
Copy link
Contributor

I have a similar problem when I try to make release on my local desktop:

+++ [1006 10:05:00] Syncing sources to container
rsync: failed to connect to 127.0.0.1 (127.0.0.1): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(128) [sender=3.1.0]
!!! Error in ./hack/../build/../build/common.sh:689
  'rsync ${rsync_extra} --archive --prune-empty-dirs --password-file="${LOCAL_OUTPUT_BUILD_CONTEXT}/rsyncd.password" --filter='- /.git/' --filter='- /.make/' --filter='- /_tmp/' --filter='- /_output/' --filter='- /' "${KUBE_ROOT}/" "rsync://k8s@${KUBE_RSYNC_ADDR}/k8s/"' exited with status 10
Call stack:
  1: ./hack/../build/../build/common.sh:689 kube::build::sync_to_container(...)
  2: ./hack/../build/../build/common.sh:433 kube::build::build_image(...)
  3: ./hack/../build/release.sh:35 main(...)
Exiting with status 1

@0xmichalis 0xmichalis mentioned this issue Oct 6, 2016
Merged
@ixdy ixdy assigned jbeda and unassigned fejta Oct 6, 2016
@ixdy
Copy link
Member

ixdy commented Oct 6, 2016

Related to #30787.

@MrHohn
Copy link
Member

MrHohn commented Oct 6, 2016

Similar problem for make quick-release:

$ make quick-release                                    
+++ [1006 10:36:15] Verifying Prerequisites....                                                           
+++ [1006 10:36:15] Building Docker image kube-build:build-f830ab5531-3-v1.6.3-9                          
+++ [1006 10:36:26] Creating data container kube-build-data-f830ab5531-3-v1.6.3-9                         
+++ [1006 10:36:27] Syncing sources to container                                                          
rsync: failed to connect to 127.0.0.1 (127.0.0.1): Connection refused (111)                               
rsync error: error in socket IO (code 10) at clientserver.c(128) [sender=3.1.0]                           
make: *** [quick-release] Error 1

@jbeda
Copy link
Contributor

jbeda commented Oct 6, 2016

@jszczepkowski Can you open a new issue for your problem with information about your set up. Mac/Linux? Docker version? etc.

@jbeda
Copy link
Contributor

jbeda commented Oct 6, 2016

@MrHohn Please add details to @jszczepkowski's (to be opened) issue. I suspect that is a different issue.

jbeda added a commit to jbeda/kubernetes that referenced this issue Oct 6, 2016
@jbeda
Use rsync to probe for rsync ready
f53bf6b 
We were using netcat to try and figure out when the rsync container is ready. Now we instead use rsync itself. I suspect that there was a race condition with some versions of Docker where it would accept connections and then close them during container start.

This fixes kubernetes#34214 (I think)
@jbeda jbeda mentioned this issue Oct 6, 2016
Merged
jbeda added a commit to jbeda/kubernetes that referenced this issue Oct 6, 2016
@jbeda
Use rsync to probe for rsync ready
add137c 
We were using netcat to try and figure out when the rsync container is ready. Now we instead use rsync itself. I suspect that there was a race condition with some versions of Docker where it would accept connections and then close them during container start.

This fixes kubernetes#34214 (I think)
k8s-github-robot pushed a commit that referenced this issue Oct 7, 2016
Merge pull request #34257 from jbeda/rsync-fix
15b9583 
Automatic merge from submit-queue

Use rsync to probe for rsync ready

We were using netcat to try and figure out when the rsync container is ready. Now we instead use rsync itself. I suspect that there was a race condition with some versions of Docker where it would accept connections and then close them during container start.

This fixes #34214 (I think)
@jszczepkowski
Copy link
Contributor

Can you open a new issue for your problem with information about your set up. Mac/Linux? Docker version? etc.

New issue: #34309

maxwell92 pushed a commit to maxwell92/kubernetes that referenced this issue Oct 8, 2016
@jbeda @maxwell92
Use rsync to probe for rsync ready
27f3830 
We were using netcat to try and figure out when the rsync container is ready. Now we instead use rsync itself. I suspect that there was a race condition with some versions of Docker where it would accept connections and then close them during container start.

This fixes kubernetes#34214 (I think)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jbeda jbeda

Labels
area/build-release area/test-infra kind/flake Categorizes issue or PR as related to a flaky test. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use rsync to probe for rsync ready jbeda/kubernetes
6 participants
@jbeda @fejta @ixdy @MrHohn @wojtek-t @jszczepkowski