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

Log start of cluster sync #2823

Merged
merged 1 commit into from
Feb 6, 2020
Merged

Log start of cluster sync #2823

merged 1 commit into from
Feb 6, 2020

Conversation

borancar
Copy link
Contributor

@borancar borancar commented Feb 5, 2020

It's helpful to operators to understand at which commit the cluster is
stuck should any errors occur with cluster sync, such as k8s internal
issues:

@borancar borancar requested review from squaremo and hiddeco February 5, 2020 11:46
@borancar
Copy link
Contributor Author

borancar commented Feb 5, 2020

To give some more context, I spent time looking at all the wrong places why the cluster wasn't getting updated until I finally got Delve and narrowed down the issue. The following 2 messages were actually not very helpful in understanding why the images were stuck at their old version:

ts=2020-02-04T20:29:52.312079303Z caller=main.go:267 type="internal kubernetes error" kubernetes_caller=k8s.io/[email protected]+incompatible/discovery/cached/memory/memcache.go:199 err="couldn't get resource list for admission.certmanager.k8s.io/v1beta1: the server is currently unable to handle the request"
ts=2020-02-04T20:29:52.329078854Z caller=main.go:267 type="internal kubernetes error" kubernetes_caller=k8s.io/[email protected]+incompatible/discovery/cached/memory/memcache.go:111 err="couldn't get resource list for admission.certmanager.k8s.io/v1beta1: the server is currently unable to handle the request"

Having those messages after a message saying "Trying/Attempting sync..." with specific git versions would have helped me massively narrow down on the issue.

@borancar borancar requested a review from hiddeco February 5, 2020 11:59
@hiddeco hiddeco added this to the 1.19.0 milestone Feb 6, 2020
@borancar borancar requested a review from hiddeco February 6, 2020 16:33
@hiddeco
Copy link
Member

hiddeco commented Feb 6, 2020

Can you please smash your commits together, edit the commit message and remove the issue links from it (to prevent endless pings to the issues from our friendly OSS neighbours), and rebase the result on master?

Copy link
Member

@hiddeco hiddeco left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your patience with the nitpicks 🌷

This adds a log line to sync similar to update. It's helpful to
operators to understand at which commit the cluster is stuck should any
errors occur with cluster sync, such as k8s internal issues.
@hiddeco hiddeco merged commit 8b676b0 into fluxcd:master Feb 6, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants