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

Operator Update failing in new operator-sdk 1.x format #2019

Closed
Kaitou786 opened this issue Feb 25, 2021 · 3 comments
Closed

Operator Update failing in new operator-sdk 1.x format #2019

Kaitou786 opened this issue Feb 25, 2021 · 3 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@Kaitou786
Copy link

Kaitou786 commented Feb 25, 2021

Bug Report

What did you do?
Hi, we recently updated our operator to follow operator-sdk 1.x, and seems to be working nicely, we already released a version of our operator built with this new format and the upgrade was working seamlessly. Now when we are trying to update our operator with the second release with this 1.x format, we see errors in the installPlans.

1 queueinformer_operator.go:290] sync {"update" "openshift-operators/install-qtcfj"} failed: error updating service: kogito-operator-controller-manager-metrics-service: Service "kogito-operator-controller-manager-metrics-service" is invalid: [metadata.resourceVersion: Invalid value: "": must be specified for an update, spec.clusterIP: Invalid value: "": field is immutable]

The manager-metrics-service is introduced with 1.x updates and now causing the problem while upgrading the operator.

What did you expect to see?
The operator should successfully be updated without any problem

What did you see instead? Under which circumstances?
The installPlan failed while updating the metricsService

Environment

  • operator-lifecycle-manager version: Not sure, version bundled with OCP I guess
  • Kubernetes version information: OCP 4.6.15

  • Kubernetes cluster kind: Openshift

Possible Solution

Additional context
Add any other context about the problem here.

@Kaitou786 Kaitou786 added the kind/bug Categorizes issue or PR as related to a bug. label Feb 25, 2021
@benluddy
Copy link
Contributor

This bug has been fixed. For OpenShift, you'll need to be on at least 4.6.16 (https://bugzilla.redhat.com/show_bug.cgi?id=1920873).

@benluddy
Copy link
Contributor

#1884

@zach-source
Copy link

@benluddy I'm seeing this same failure on 4.5. Is there a patch fix planned for this on that release?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

3 participants