You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 5, 2024. It is now read-only.
I find an error when deploy with SEO 22.04.02
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: TypeError: deprecated() got an unexpected keyword argument 'name'
fatal: [controller]: FAILED! => {
"attempts": 10,
"changed": false,
"rc": 1
}
MSG:
MODULE FAILURE
See stdout/stderr for the exact error
we have checked the config and run it manually.
smartedge-open@ubuntu-fb446d90bd:/opt/seo/roles/kubernetes/helm/defaults$ cat main.yml
I find an error when deploy with SEO 22.04.02
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: TypeError: deprecated() got an unexpected keyword argument 'name'
fatal: [controller]: FAILED! => {
"attempts": 10,
"changed": false,
"rc": 1
}
MSG:
MODULE FAILURE
See stdout/stderr for the exact error
we have checked the config and run it manually.
smartedge-open@ubuntu-fb446d90bd:/opt/seo/roles/kubernetes/helm/defaults$ cat main.yml
SPDX-License-Identifier: Apache-2.0
Copyright (c) 2020 Intel Corporation
_helm_version: "v3.8.0"
_helm_name: "helm-{{ _helm_version }}-linux-amd64"
_helm_download_url: "https://get.helm.sh"
_helm_download_item: "{{ _helm_name }}.tar.gz"
_helm_binary_path: /usr/local/bin/helm
however it can install by manually
smartedge-open@ubuntu-fb446d90bd:/opt/seo/roles/kubernetes/helm/defaults$ https://get.helm.sh/helm-v3.8.0-linux-amd64.tar.gz
-bash: https://get.helm.sh/helm-v3.8.0-linux-amd64.tar.gz: No such file or directory
smartedge-open@ubuntu-fb446d90bd:/opt/seo/roles/kubernetes/helm/defaults$ wget https://get.helm.sh/helm-v3.8.0-linux-amd64.tar.gz
--2022-10-10 03:38:25-- https://get.helm.sh/helm-v3.8.0-linux-amd64.tar.gz
Resolving child-prc.intel.com (child-prc.intel.com)... 10.239.120.55
Connecting to child-prc.intel.com (child-prc.intel.com)|10.239.120.55|:913... connected.
Proxy request sent, awaiting response... 200 OK
The text was updated successfully, but these errors were encountered: