-
Notifications
You must be signed in to change notification settings - Fork 35
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
Automatic upgrade to 1.0.6 failing #92
Comments
can you delete the operator deployment? OLM should recreate it for you. Please let me know how it goes. |
@raffaelespazzoli completely removing the operator 1.0.6 and then re-adding it manually solved the issue. My 1.0.5 was in a different namespace as the default suggested, so that could have caused the hick-up maybe? on OCP 4.7 |
I had to remove the 1.0.5 subscription and uninstall the failing 1.0.6 operator and the reinstall the 1.0.6 operator. Using default namespace |
Sorry for the problem this has caused. The namespace should not matter. Any
chance you saved the error logs?
…On Thu, Jun 3, 2021, 5:55 AM Christian Haller ***@***.***> wrote:
I had to remove the 1.0.5 subscription and uninstall the failing 1.0.6
operator and the reinstall the 1.0.6 operator. Using default namespace
cert-utils-operator.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#92 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABPERXETCZ6UGWHJ5HGWC5LTQ5GQ7ANCNFSM45676YNQ>
.
|
Yes, full logs available in Elasticsearch, which ones do you need?
|
I see. No need for other logs. Unfortunately that change was needed to
allow for multiple operators to be installed in the same namespace. Also
unfortunately all the CoP operators will be affected.
I believe the easier way to solve this is to just delete the operator
deployment. OLM should recreate it with the new upgraded template.
…On Thu, Jun 3, 2021 at 7:25 AM Christian Haller ***@***.***> wrote:
Yes, full logs available in Elasticsearch, which ones do you need?
OLM logged:
I0603 07:59:58.724388 1 event.go:282] Event(v1.ObjectReference{Kind:"ClusterServiceVersion", Namespace:"cert-utils-operator", Name:"cert-utils-operator.v1.0.6", UID:"ced69576-1c5e-4588-81cd-0c86b85be683", APIVersion:"operators.coreos.com/v1alpha1", ResourceVersion:"613758835", FieldPath:""}): type: 'Warning' reason: 'InstallComponentFailed' install strategy failed: Deployment.apps "cert-utils-operator-controller-manager" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"operator":"cert-utils-operator"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#92 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABPERXGGU5WIKF7DNPN5PALTQ5RCPANCNFSM45676YNQ>
.
--
ciao/bye
Raffaele
|
Upgrading from 1.0.5 via automatic strategy seems to be failing. Relevant event is:
The text was updated successfully, but these errors were encountered: