Tanzu Framework provides a set of building blocks to build atop of the Tanzu platform and leverages Carvel packaging and plugins to provide users with a much stronger, more integrated experience than the loose coupling and stand-alone commands of the previous generation of tools.
Apache License 2.0
197
stars
193
forks
source link
Trace logging on checking plugins after management cluster creation #1727
There are a bunch of trace debug log messages that get emitted to the console at the end of management cluster creation.
Checking for required plugins...
I0223 14:56:39.757441 938359 request.go:665] Waited for 1.185487904s due to client-side throttling, not priority and fairness, request: GET:https://172.18.0.3:6443/apis/controlplane.cluster.x-k8s.io/v1alpha3?timeout=32s
I0223 14:56:49.757654 938359 request.go:665] Waited for 11.185636681s due to client-side throttling, not priority and fairness, request: GET:https://172.18.0.3:6443/apis/ops.antrea.tanzu.vmware.com/v1alpha1?timeout=32s
All required plugins are already installed and up-to-date
This looks like log file lines that should not be printed to the console.
Affected product area (please put an X in all that apply)
[ ] APIs
[ ] Addons
[X] CLI
[ ] Docs
[ ] IAM
[ ] Installation
[ ] Plugin
[ ] Security
[ ] Test and Release
[X] User Experience
Expected behavior
No debug log formatted messages printed to the console.
Steps to reproduce the bug
Run tanzu management-cluster create
Version (include the SHA if the version is not obvious)
v0.17.0
$ tanzu version
version: v0.18.0-dev
buildDate: 2022-02-23
sha: a240fe5a
Environment where the bug was observed (cloud, OS, etc)
Testing locally with docker, but appears to be non-provider specific.
Bug description
There are a bunch of trace debug log messages that get emitted to the console at the end of management cluster creation.
This looks like log file lines that should not be printed to the console.
Affected product area (please put an X in all that apply)
Expected behavior
No debug log formatted messages printed to the console.
Steps to reproduce the bug
Run
tanzu management-cluster create
Version (include the SHA if the version is not obvious)
v0.17.0
Environment where the bug was observed (cloud, OS, etc)
Testing locally with docker, but appears to be non-provider specific.
Relevant Debug Output (Logs, manifests, etc)