Skip to content
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.

Be more specific with the feedback from git #1170

Closed
squaremo opened this issue Jun 26, 2018 · 0 comments
Closed

Be more specific with the feedback from git #1170

squaremo opened this issue Jun 26, 2018 · 0 comments
Labels
☠ high user impact onboarding/activation Particular pertinence to getting Flux up and running

Comments

@squaremo
Copy link
Member

When git has not quite been set up, because it needs a custom known_hosts or whatnot, the flux daemon constantly logs

caller=images.go:21 component=sync-loop error="getting unlocked automated services: git repo not ready"

and this is something of a misdirection. In part because it's not the underlying problem, just the visible one; but mainly because it doesn't say anything about why.

Logging the git mirroring attempts, and what is not happening, would be a good start. Suppressing the above line, or at least only reporting on state changes, would also be useful.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
☠ high user impact onboarding/activation Particular pertinence to getting Flux up and running
Projects
None yet
Development

No branches or pull requests

1 participant