Skip to content
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

Merged
merged 5 commits into from
May 3, 2022

Conversation

phantomjinx
Copy link
Contributor

Release Note

Using `kamel install -v debug`, it is now possible to switch on debug logging messages in the operator pod log. The `-v` switch has the effect of adding an environment variable (LOG_LEVEL) to the operator deployment resource. The value of this variable can be either `info`, `debug` or an integer. 

* 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
Copy link
Contributor

@squakez squakez left a 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.

pkg/cmd/install.go Outdated Show resolved Hide resolved
* 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
@phantomjinx
Copy link
Contributor Author

There is some lint complains. The other E2E failures looks to be something failing in general and we must fix anyway.

Hopefully fixed them.

@phantomjinx
Copy link
Contributor Author

I believe #3246 is what is making the Upgrade test fail.

@oscerd
Copy link
Contributor

oscerd commented May 3, 2022

Tests seems to be failing, not only upgrade.

@squakez
Copy link
Contributor

squakez commented May 3, 2022

Tests seems to be failing, not only upgrade.

Yes, there is already something else broken on main. I'll merge this as it partially fixes things. Later we should focus on what else is failing.

@squakez squakez merged commit 45d976e into apache:main May 3, 2022
@oscerd
Copy link
Contributor

oscerd commented May 3, 2022

Let me know when we want to start release 1.9.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants