namespace-configuration-operator icon indicating copy to clipboard operation
namespace-configuration-operator copied to clipboard

Upgrade fails from 1.2.2 -> 1.2.3

Open davidkarlsen opened this issue 3 years ago • 2 comments

2m24s       Normal    BeingReplaced            clusterserviceversion/namespace-configuration-operator.v1.2.2   being replaced by csv: namespace-configuration-operator.v1.2.3
2m24s       Normal    RequirementsUnknown      clusterserviceversion/namespace-configuration-operator.v1.2.3   requirements not yet checked
2m23s       Normal    RequirementsNotMet       clusterserviceversion/namespace-configuration-operator.v1.2.3   one or more requirements couldn't be found
2m2s        Normal    AllRequirementsMet       clusterserviceversion/namespace-configuration-operator.v1.2.3   all requirements found, attempting install
2m1s        Warning   InstallComponentFailed   clusterserviceversion/namespace-configuration-operator.v1.2.3   install strategy failed: Deployment.apps "namespace-configuration-operator-controller-manager" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"control-plane":"namespace-configuration-operator"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable
2m4s        Normal    NeedsReinstall           clusterserviceversion/namespace-configuration-operator.v1.2.3   installing: missing deployment with name=namespace-configuration-operator-controller-manager

The workaround is to delete the existing deployment.

The reason is that the matchers changed from:

 selector:
      matchLabels:
        operator: namespace-configuration-operator

TO

  matchLabels:
        control-plane: namespace-configuration-operator

same applies to the cert-utils-operator

davidkarlsen avatar Apr 19 '22 10:04 davidkarlsen

Hi.

Will the namespaces created via the operator be removed when uninstalling the operator as part of the workaround? Don't have a spare environment to test this before doing it on the cluster used by the clients.

Thanks!

chitic-andrei avatar May 04 '22 07:05 chitic-andrei

no they will not be removed and apologies for the inconvenience generated by this release

On Wed, May 4, 2022 at 3:23 AM Andrei Chitic @.***> wrote:

Hi.

Will the namespaces created via the operator will be removed when uninstalling it as part of the workaround? Don't have a spare environment to test this before doing it on the cluster used by the clients.

Thanks!

— Reply to this email directly, view it on GitHub https://github.com/redhat-cop/namespace-configuration-operator/issues/129#issuecomment-1117002771, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABPERXAYF5AV6BYGPEAZT6LVIIQXRANCNFSM5TYMT7HQ . You are receiving this because you are subscribed to this thread.Message ID: <redhat-cop/namespace-configuration-operator/issues/129/1117002771@ github.com>

-- ciao/bye Raffaele

raffaelespazzoli avatar May 04 '22 12:05 raffaelespazzoli