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
  3. MAISTRA-1986

Create a test case that covers upgrading from 1.1.x to 2.0.0 with an invalid set within SMCP definition


    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Major Major
    • maistra-2.0.0
    • None
    • None
    • None
    • MAISTRA 2.0.0

      A bug was found (MAISTRA-1983) that, if a set within SMCP is set to an invalid type, it breaks the upgrade process. 

      This can be easily reproduced by taking the example of the bug description. As QE, we should add this case into our upgrade portfolio test cases so we can make sure the upgrade process is more resilient from such mistake. 

            rh-ee-gbaufake Guilherme Baufaker Rego
            tmoreira@redhat.com Tiago Moreira Vieira (Inactive)
            0 Vote for this issue
            1 Start watching this issue