-
Notifications
You must be signed in to change notification settings - Fork 504
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
invalid argument issue after 0.69.0 upgrade #1339
Comments
Hey @jihuiyang! I'm here to help you with any bugs, questions, or contributions. Let's tackle this together! I found a similar open issue that might be relevant to your problem: [operator] Collector fails with featureGate errors when Upgrading the Operator to chart version 0.68.1. The issue you're encountering with the OpenTelemetry collector failing with featureGate errors is due to changes in the To resolve this issue, you need to ensure that your CRDs are properly annotated and labeled before upgrading. Here are the steps:
Additionally, if you are upgrading from version 0.67 to 0.68, note that the This issue is a known bug and will be fixed by this PR in the operator: open-telemetry/opentelemetry-operator#3074. This fix will be included in the next operator helm release [1]. |
bug still exists in latest operator version |
@jihuiyang You cannot disable the confmap.unifyEnvVarExpansion feature gate anymore. Doing --feature-gates= -confmap.unifyEnvVarExpansion is not allowed |
I did not specify |
maybe i should uninstall and whole thing and reinstall? |
@jihuiyang I haven't been able to reproduce your issue yet with a clean install or with a |
@jihuiyang the latest version of the operator should resolve this by removing the gate from a collector (we previously needed to add this to the operator's code to prevent users from config from breaking from a collector change) Can you link any logs you are seeing from the operator? |
I tried a clean install and it worked without the |
@jihuiyang thanks for trying that out. I have been debugging the upgrade process in this issue, if you run into a similar issue during the upgrade I would really appreciate if you could share the steps to reproduce. I've tried a few different ways of doing this and have yet to cause it to happen. |
still running into the issue with upgrade, upgrading from 0.65.1 to 0.69
Collector still sees the featuregate
Operator log
|
if you do this, do you see the string 'managed'?
|
yes i do
|
I also experienced this. I had to delete and recreate the OpentelemetryCollector resource (type = sidecar, in my case). |
I'm also having a similar issue upgrading from 0.69.0 to 0.74.2 - The collector is failing to start, and logging |
@ethanmdavidson this should have been fixed in the release for https://github.com/open-telemetry/opentelemetry-operator/releases/tag/v0.110.0... I think this may be if the rollout for the operator is slow and an old version is still adding it. I had tried to repro this a few times and never was able to. |
otel collectors are failing after 0.69.0 upgrade
when i describe the container i can see
-confmap.unifyEnvVarExpansion
, looks like new version 0.108.0 does not like itThe text was updated successfully, but these errors were encountered: