Uploaded image for project: 'Maistra'
  1. Maistra
  2. MAISTRA-1983

Upgrading to 2.0.0 with an existing SMCP considered invalid cannot easily be repaired


    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • maistra-2.0.0
    • None
    • None
    • None
    • MAISTRA 2.0.0

      If a user has a pre-existing SMCP which is invalid, for example defining an attribute as null when it is expected to be a string, then it is not possible to fix without deleting the operator and CRDs.

      Validation will fail with an error, for example as follows

      Error from server: error when creating "smcp.yaml": conversion webhook for maistra.io/v1, Kind=ServiceMeshControlPlane failed: .redundancyPolicy accessor error: <nil> is of the type <nil>, expected string

      and this prevents any manipulation of the resource (edit/delete etc).

      The only fix appears to be uninstall the operator and delete the CRDs, tidying up the resource, and then a clean installation with the fixed SMCP.

        1. smcp-test-2.0.0-1.png
          85 kB
        2. smcp.yaml
          2 kB
        3. error-on-2.0.0-0.png
          164 kB
        4. 2.0.0-1-upgrade.png
          215 kB

            rh-ee-gbaufake Guilherme Baufaker Rego
            kconner@redhat.com Kevin Conner (Inactive)
            0 Vote for this issue
            6 Start watching this issue