DC Upgrade Activate failure due to nginx_ingress_controller_manifest update failure

[Lucas]

Brief Description
-----------------
Subcloud upgrade activation failure due to nginx_ingress_controller_manifest update from version from 21.12-18 to 22.06-37 was failed.

This is due to a plugin name collision with other plugins

Severity
--------
Critical: Cannot apply nginx

Steps to Reproduce
------------------
1.    Install DC system with stx6.0 and the latest patches.
2.    Upgrade the Central cloud
3.    Upgrade sub cloud  upgrade activation was failing due to update nginx_ingress_controller_manifest update was failed

Expected Behavior
------------------
Able activate with nginx_ingress_controller_manifest

Actual Behavior
----------------
Update nginx_ingress_controller_manifest was failed and activation failed.

Reproducibility
---------------
Reproducible
System Configuration
--------------------
all

Branch/Pull Time/Commit
-----------------------
master

Last Pass
---------
stx6.0

Timestamp/Logs
--------------
|cert-manager            |22.06-37|cert-manager-fluxcd-manifests    |fluxcd-manifests  |applied      |completed        |
|nginx-ingress-controller|21.12-18|nginx-ingress-controller-manifest|nginx_ingress_con|apply-failed|Application      |
|                         |         |                                 |troller_manifest.|             |update from      |
|                         |         |                                 |yaml              |             |version 21.12-18|
|                         |         |                                 |                 |             |to version 22.  |
|                         |         |                                 |                 |             |06-37 aborted.  |
|                         |         |                                 |                 |             |Application      |
|                         |         |                                 |                 |             |recover to      |
|                         |         |                                 |                 |             |version 21.12-18|
|                         |         |                                 |                 |             |aborted. Please  |
|                         |         |                                 |                 |             |check logs for  |
|                         |         |                                 |                 |             |details.        |
|                         |         |                                 |                 |             |                 |
|oidc-auth-apps          |21.12-61|oidc-auth-manifest                |manifest.yaml    |uploaded    |completed        |
|platform-integ-apps      |21.12-44|platform-integration-manifest    |manifest.yaml    |applied      |completed        |
|rook-ceph-apps          |1.0-14  |rook-ceph-manifest                |manifest.yaml    |uploaded    |completed        |

Test Activity
-------------
Feature Testing

Workaround
----------
delete nginx and reapply

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/starlingx/nginx-ingress-controller-armada-app/+/848317

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/starlingx/nginx-ingress-controller-armada-app/+/848317
Committed: https://opendev.org/starlingx/nginx-ingress-controller-armada-app/commit/1f419fd6534236ba37bb7393e7f7653f2159bd20
Submitter: "Zuul (22348)"
Branch: master

commit 1f419fd6534236ba37bb7393e7f7653f2159bd20
Author: Lucas Cavalcante <email address hidden>
Date: Thu Jun 30 13:46:26 2022 -0300

    Fix Nginx Controller Helm plugin name collision

    If a Helm plugin from app (X) has the same name as other plugin from a
    different app (Y), app plugins from X is not installed as there is a
    plugin with the same name already installed. Internally Sysinv
    AppOperator has a HashTable and its key is the plugin name, therefore
    preventing adding plugins with same name.

    We change nginx plugin name so that other apps with different nginx
    pĺugins don't collide and prevent the platform from being able to
    apply/reapply nginx-platfrom-app

    001_ingres-nginx -> 0001_ks-ingress-nginx

    Test Plan:
    PASS: Apply Nginx together with an app with previous nginx plugin
    name
    PASS: Name changed at system overrides, command:
    system helm-override-show nginx-ingress-controller
    nginx-ingress-controller kube-system

    Closes-bug: 1980394
    Signed-off-by: Lucas Cavalcante <email address hidden>
    Change-Id: I2a1b663d3867873d024c108d71ee074da1a39a5e