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

SD2 marks development host as "unhealthy" (SHOU) when an RSYNC fails #5

Open
iliasbfff opened this issue Jan 9, 2019 · 0 comments
Open

SD2 marks development host as "unhealthy" (SHOU) when an RSYNC fails #5

iliasbfff opened this issue Jan 9, 2019 · 0 comments

Comments

@iliasbfff
Copy link

Steps to reproduce:

  • In your editing host (own workspace) remove a folder that is supposed to be RSYNCed. In my case it was the .kube folder.

  • After sd2 is running and the containers on the development machine are up and running, kill a container

  • According to the logs an RSYNC for the missing directory fails, and the development host is eventually marked as unhealthy, causing sd2 to skip checks for docker.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@iliasbfff