Comment 0 for bug 1978899

Brief Description
-----------------
Restore fails executing the Ansible restore playbook on Storage system with IPv4.

Severity
--------
<Critical: System/Feature is not usable after the defect>

Steps to Reproduce
------------------
- Install duplex system with WRCP 22.06 GA on IPv4 system
- Run the Backup Ansible playbook from controller-0
- Install a clean image of WRCP in the system and wipedisk=false
- Run the restore Ansible playbook with the backup file saved above

Expected Behavior
------------------
Run the Ansible restore playbook and unlock controller-0 and controller-1 sucessfully

Actual Behavior
----------------
Ansible restore playbook fails.

Reproducibility
---------------
Reproducible 2/2

System Configuration
--------------------
AIO-SX
AIO-DX
Storage

Last Pass
---------
This test was not run for a long time on storage.

On duplex systems:
SW_VERSION="22.02"
BUILD_TARGET="Host Installer"
BUILD_TYPE="Formal"
BUILD_ID="2022-04-05_20-00-06"
SRC_BUILD_ID="1227"

On AIO-SX:
SW_VERSION="22.02"
BUILD_TARGET="Host Installer"
BUILD_TYPE="Formal"
BUILD_ID="2022-04-03_20-00-06"
SRC_BUILD_ID="1225"

Timestamp/Logs
--------------
E TASK [common/armada-helm : Launch Armada with Helm v3] ***************************************************************************************************************************************************************************************************
E Wednesday 04 May 2022 11:52:01 +0000 (0:00:01.308) 0:19:47.823 *********
E fatal: [localhost]: FAILED! => changed=true 
E  cmd:
E  - /sbin/helm
E  - upgrade
E  - --install
E  - armada
E  - stx-platform/armada
E  - --namespace
E  - armada
E  - --values
E  - /tmp/armada-overrides.yaml
E  - --debug
E  delta: '0:00:00.480501'
E  end: '2022-05-04 11:52:02.174253'
E  msg: non-zero return code
E  rc: 1
E  start: '2022-05-04 11:52:01.693752'
E  stderr: |-
E  history.go:52: [debug] getting history for release armada
E  install.go:159: [debug] Original chart version: ""
E  install.go:176: [debug] CHART PATH: /home/sysadmin/.cache/helm/repository/armada-0.1.0.tgz
E  
E  client.go:108: [debug] creating 10 resource(s)
E  Error: Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": Post "https://ic-nginx-ingress-ingress-nginx-controller-admission.kube-system.svc:443/networking/v1beta1/ingresses?timeout=10s": dial tcp 10.102.163.201:443: connect: connection refused
E  helm.go:84: [debug] Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": Post "https://ic-nginx-ingress-ingress-nginx-controller-admission.kube-system.svc:443/networking/v1beta1/ingresses?timeout=10s": dial tcp 10.102.163.201:443: connect: connection refused
E  stderr_lines:
E  - 'history.go:52: [debug] getting history for release armada'
E  - 'install.go:159: [debug] Original chart version: ""'
E  - 'install.go:176: [debug] CHART PATH: /home/sysadmin/.cache/helm/repository/armada-0.1.0.tgz'
E  - ''
E  - 'client.go:108: [debug] creating 10 resource(s)'
E  - 'Error: Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": Post "https://ic-nginx-ingress-ingress-nginx-controller-admission.kube-system.svc:443/networking/v1beta1/ingresses?timeout=10s": dial tcp 10.102.163.201:443: connect: connection refused'
E  - 'helm.go:84: [debug] Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": Post "https://ic-nginx-ingress-ingress-nginx-controller-admission.kube-system.svc:443/networking/v1beta1/ingresses?timeout=10s": dial tcp 10.102.163.201:443: connect: connection refused'
E  stdout: Release "armada" does not exist. Installing it now.
E  stdout_lines: <omitted>
E
E PLAY RECAP

Test Activity
-------------
Regression Testing

Workaround
----------
for vms: exit and reconnect to the vm. The kubernetes becomes accessible againand it can finish the restore after deleting /etc/platform.restore*