-
Notifications
You must be signed in to change notification settings - Fork 561
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.
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
A few suspicious logs #1976
Comments
Can you gist Can you gist |
Which log is the |
The KCM is issuing the partial object metadata error
|
Can you gist the full KCM log? |
https://gist.github.com/cd426e125a2355bcecfe9cf2f124a363 <- |
(deleted this comment as the kcm logs were unusable, they were from a non-active kcm, will add them back when i see this again) |
@jayunit100 if you can reproduce this, please let us know, and we'll see about triaging it together with a screenshare. /priority awaiting-more-evidence |
Maybe 2 is related to kubernetes/kubernetes#79610 ? |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
/close |
@randomvariable: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/kind bug
what is the bug
There are suspicious logs in CAPA apiserver and controller manager in the latest capa release . These might be non-issues (conformance tests seem to hum along happily) , but they seem like they might indicate other problems which might relate to managment polling or MHC or ... So just logging my thoughts here.
The three logs im seeing
what steps did you take to reproduce the bug
Spun up a mostly vanilla cluster on capa 0.5.6 using TKG
Details
Inside a see a few suspicious log messages, these may not be important, but seem a little scary.
These appear in the apiserver from time to time.
which appear in the KCM
What steps did you take and what happened:
These are fresh CAPA clusters spun up using the TKG platform
What did you expect to happen:
any labels on pods would work properly with watches , and in general new clusters wouldnt have failing queries during conformance test runs
Anything else you would like to add:
I was running the K8s conformance suite via sonobuoy when seeing these. i havent yet determined wether it is the cause of these errors though or what is running these queries
Environment:
kubectl version
): 1.19/etc/os-release
):The text was updated successfully, but these errors were encountered: