-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
bundle validate
does not respect the --verbose-flag
#3793
Labels
language/go
Issue is related to a Go operator project
Comments
openshift-ci-robot
added
the
language/go
Issue is related to a Go operator project
label
Aug 27, 2020
JAORMX
added a commit
to JAORMX/operator-sdk
that referenced
this issue
Aug 27, 2020
This makes the bundle validate subcommand respect the verbosity level by setting it directly in the logger that's actually used, and not in the global logger as was done previously. Closes: operator-framework#3793
This was referenced Aug 27, 2020
JAORMX
added a commit
to JAORMX/operator-sdk
that referenced
this issue
Aug 27, 2020
This makes the bundle validate subcommand respect the verbosity level by setting it directly in the logger that's actually used, and not in the global logger as was done previously. Closes: operator-framework#3793
JAORMX
added a commit
to JAORMX/operator-sdk
that referenced
this issue
Aug 27, 2020
This makes the bundle validate subcommand respect the verbosity level by setting it directly in the logger that's actually used, and not in the global logger as was done previously. Closes: operator-framework#3793
JAORMX
added a commit
to JAORMX/operator-sdk
that referenced
this issue
Aug 28, 2020
This makes the bundle validate subcommand respect the verbosity level by setting it directly in the logger that's actually used, and not in the global logger as was done previously. Closes: operator-framework#3793
asmacdo
added a commit
that referenced
this issue
Aug 28, 2020
* Make bundle validate subcommand respect verbosity This makes the bundle validate subcommand respect the verbosity level by setting it directly in the logger that's actually used, and not in the global logger as was done previously. Closes: #3793 * add unit test Co-authored-by: Austin Macdonald <austin@redhat.com>
asmacdo
added a commit
to asmacdo/operator-sdk
that referenced
this issue
Aug 28, 2020
…#3795) * Make bundle validate subcommand respect verbosity This makes the bundle validate subcommand respect the verbosity level by setting it directly in the logger that's actually used, and not in the global logger as was done previously. Closes: operator-framework#3793 * add unit test Co-authored-by: Austin Macdonald <austin@redhat.com>
asmacdo
added a commit
that referenced
this issue
Aug 28, 2020
* Make bundle validate subcommand respect verbosity This makes the bundle validate subcommand respect the verbosity level by setting it directly in the logger that's actually used, and not in the global logger as was done previously. Closes: #3793 * add unit test Co-authored-by: Austin Macdonald <austin@redhat.com> Co-authored-by: Juan Osorio Robles <jaosorior@redhat.com>
joelanford
pushed a commit
to joelanford/operator-sdk
that referenced
this issue
Sep 17, 2020
…#3795) * Make bundle validate subcommand respect verbosity This makes the bundle validate subcommand respect the verbosity level by setting it directly in the logger that's actually used, and not in the global logger as was done previously. Closes: operator-framework#3793 * add unit test Co-authored-by: Austin Macdonald <austin@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
What did you do?
When running
operator-sdk bundle validate
with the verbose flag, I expected to get some debugging output.What did you expect to see?
What I expected to see, for instance, was the arguments that the command uses to call podman.
When forcing the debug flag on to the logger that the command uses, I expected to see something like the following:
What did you see instead? Under which circumstances?
As seen below, the debug (verbose) flag is detected, but the output does not reflect what it should.
Environment
Operator type:
/language go
Kubernetes cluster type:
OpenShift
$ operator-sdk version
v0.18.2
$ go version
(if language is Go)go version go1.14.6 linux/amd64
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.2-0-g52c56ce", GitCommit:"5fbf625fade0eb366cccaab717100a88d5d18a4a", GitTreeState:"clean", BuildDate:"2020-08-26T03:39:18Z", GoVersion:"go1.14.4", Compiler:"gc", Platform:"linux/amd64"}
Possible Solution
Set the verbosity level in the actual logger instance that's used.
The text was updated successfully, but these errors were encountered: