| 2022-06-16 13:42:59 |
João Pedro Alexandroni Cordova de Sousa |
description |
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 [0;31mfatal: [localhost]: FAILED! => changed=true [0m
E [0;31m cmd:[0m
E [0;31m - /sbin/helm[0m
E [0;31m - upgrade[0m
E [0;31m - --install[0m
E [0;31m - armada[0m
E [0;31m - stx-platform/armada[0m
E [0;31m - --namespace[0m
E [0;31m - armada[0m
E [0;31m - --values[0m
E [0;31m - /tmp/armada-overrides.yaml[0m
E [0;31m - --debug[0m
E [0;31m delta: '0:00:00.480501'[0m
E [0;31m end: '2022-05-04 11:52:02.174253'[0m
E [0;31m msg: non-zero return code[0m
E [0;31m rc: 1[0m
E [0;31m start: '2022-05-04 11:52:01.693752'[0m
E [0;31m stderr: |-[0m
E [0;31m history.go:52: [debug] getting history for release armada[0m
E [0;31m install.go:159: [debug] Original chart version: ""[0m
E [0;31m install.go:176: [debug] CHART PATH: /home/sysadmin/.cache/helm/repository/armada-0.1.0.tgz[0m
E [0;31m [0m
E [0;31m client.go:108: [debug] creating 10 resource(s)[0m
E [0;31m 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[0m
E [0;31m 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[0m
E [0;31m stderr_lines:[0m
E [0;31m - 'history.go:52: [debug] getting history for release armada'[0m
E [0;31m - 'install.go:159: [debug] Original chart version: ""'[0m
E [0;31m - 'install.go:176: [debug] CHART PATH: /home/sysadmin/.cache/helm/repository/armada-0.1.0.tgz'[0m
E [0;31m - ''[0m
E [0;31m - 'client.go:108: [debug] creating 10 resource(s)'[0m
E [0;31m - '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'[0m
E [0;31m - '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'[0m
E [0;31m stdout: Release "armada" does not exist. Installing it now.[0m
E [0;31m stdout_lines: <omitted>[0m
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* |
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 Starlingx on IPv4 system
- Run the Backup Ansible playbook from controller-0
- Install a clean image of Starlingx 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 [0;31mfatal: [localhost]: FAILED! => changed=true [0m
E [0;31m cmd:[0m
E [0;31m - /sbin/helm[0m
E [0;31m - upgrade[0m
E [0;31m - --install[0m
E [0;31m - armada[0m
E [0;31m - stx-platform/armada[0m
E [0;31m - --namespace[0m
E [0;31m - armada[0m
E [0;31m - --values[0m
E [0;31m - /tmp/armada-overrides.yaml[0m
E [0;31m - --debug[0m
E [0;31m delta: '0:00:00.480501'[0m
E [0;31m end: '2022-05-04 11:52:02.174253'[0m
E [0;31m msg: non-zero return code[0m
E [0;31m rc: 1[0m
E [0;31m start: '2022-05-04 11:52:01.693752'[0m
E [0;31m stderr: |-[0m
E [0;31m history.go:52: [debug] getting history for release armada[0m
E [0;31m install.go:159: [debug] Original chart version: ""[0m
E [0;31m install.go:176: [debug] CHART PATH: /home/sysadmin/.cache/helm/repository/armada-0.1.0.tgz[0m
E [0;31m [0m
E [0;31m client.go:108: [debug] creating 10 resource(s)[0m
E [0;31m 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[0m
E [0;31m 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[0m
E [0;31m stderr_lines:[0m
E [0;31m - 'history.go:52: [debug] getting history for release armada'[0m
E [0;31m - 'install.go:159: [debug] Original chart version: ""'[0m
E [0;31m - 'install.go:176: [debug] CHART PATH: /home/sysadmin/.cache/helm/repository/armada-0.1.0.tgz'[0m
E [0;31m - ''[0m
E [0;31m - 'client.go:108: [debug] creating 10 resource(s)'[0m
E [0;31m - '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'[0m
E [0;31m - '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'[0m
E [0;31m stdout: Release "armada" does not exist. Installing it now.[0m
E [0;31m stdout_lines: <omitted>[0m
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* |
|
