-
Notifications
You must be signed in to change notification settings - Fork 345
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
#3053 #3242 Fixes e2e preflight and adds debug level to logging #3245
Conversation
* preflight-test.sh * Wait for the catalog source to become READY rather than assume it is * build-bundle-image.sh * build-index-image.sh * Change the upgrade-test channel to avoid a conflict with existing channels * .../operator.go * Functions assume existence of Config reference but this is no longer being created implicitly so add to avoid panics
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is some lint complains. The other E2E failures looks to be something failing in general and we must fix anyway.
* Exposes a switch --log-level (-v) at the CLI level allowing the operator to have its level of logging changed (info, debug, 0 ... 10) * The switch translates to an env variable LOG_LEVEL which is included in the operator deployment. It is this env var that determines the internal level of the log. * install.go * The CLI switch for setting the log-level * operator.go * The setting of the log-level based on the env variable * Adds debug logging for building the integration kits and integrations * Wraps errors when building integration kits to identify more precisely where the error is occurring and the reason
b0ddc92
to
8adc02c
Compare
Hopefully fixed them. |
07e2afd
to
52882dd
Compare
I believe #3246 is what is making the Upgrade test fail. |
Tests seems to be failing, not only upgrade. |
Yes, there is already something else broken on |
Let me know when we want to start release 1.9.1 |
Release Note