[minor] Review fvt-launcher design for manage and its dependencies

[alequint]

Goal

• Review fvt-manage-is and split it in phases (all tests are running in parallel today, it will not work for selenium based on previous experience)
• Reintroduce fvt-manage-is
• Reintroduce ivt (already done in by @unnati-solanki-git in [minor] IVT launcher changes #1014, to be tested integrated with the changes in current PR)
• Move Manage's base-api-setup outside fvt-manage and make fvt-manage, fvt-manage-is and fvt-optimizer depend on it
• Review waitfor-installation task that runs at the end of fvt-launcher:
  • when installation fails too early, waitfor-installation keep waiting till sync status is Completed. Besides that, we should also make Failed as a escape route and then waitfor-configmap logic will fail pipeline earlier
• Review wait for install tasks in Layer 4 pipelines as per https://jsw.ibm.com/browse/MASCORE-2908

Evidences

About fvt-manage-is

Before:

After (in 4 phases):

Reintroduce Manage IS + Manage Setup move

• Manage-is is part of Manage, so launchfvt-manage-is must be considered like launchfvt-manag, between same waifor / approval tasks in fvt-launcher;
• Manage Setup must come before Manage, Manage IS, Optimizer and Predict

Escape Route in fvt-launcher's waitfor-installation

Considering configmap, key and value to watch:

    - name: configmap_name
       value: sync-install
    - name: configmap_key
       value: INSTALL_STATUS
    - name: configmap_target_value
       value: Completed

... added a escape route against the same map:

   - name: escape_configmap_name
      value: sync-install
   - name: escape_configmap_key
      value: INSTALL_STATUS

During the iteration, If value is not Completed, we check if that key assumed any different value, like Failed. And as Failed is different from Completed and we are not ignoring failures, task will exit in error earlier than timeout.

In addition, as per slack conversation here, wait-for-configmap has been slightly changed to consider input of config map value with more than one value (i.e. Completed and Succeeded)

About wait-for-install Tasks in Layer 4 pipelines

Evidence during uninstall pipeline (note use of wait-for-pipelinerun, repeating checking every 600 seconds, as opposed to old wait-for-install, using oc condition with 12h timeout:

Note: ansible-FVT PR supporting changes above: https://github.ibm.com/maximoappsuite/ansible-fvt/pull/433

Final Test

FVT Launcher has launched all the things properly in the right sequence:

Manage Industry Solutions pipeline running as expected (including Health):

Finally, IVT Pipeline running after manage and monitor FVTs are finished:

Note: in the screenshot we see approval-manange did not run. That is because I had not updated when criteria of that task as I did with waitfor-manage. The criteria did not consider manage-is launcher to run, only manage and mobile (and both are false in this run). I did this correction in a subsequent commit here: f04377b

Test evidence of the final sync install step in FVT Launcher, where code was modified to receive two possible target values for the config-mal key:

And here indicates that install pipeline set it up with Completed