need your help, while running viya4-deployment --tags "cluster-logging,cluster-monitoring,viya-monitoring,install" command I am getting the following error message:
/tmp/ansible.78xfu5d4/viya4-monitoring-kubernetes/monitoring/bin/deploy_monitoring_cluster.sh
delta: '0:21:46.604259'
end: '2023-06-27 07:40:32.939904'
msg: non-zero return code
rc: 1
start: '2023-06-27 07:18:46.335645'
stderr: |-
Flag --short has been deprecated, and will be removed in the future. The --short output will become the default.
Flag --short has been deprecated, and will be removed in the future. The --short output will become the default.
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /config/kubeconfig
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /config/kubeconfig
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /config/kubeconfig
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /config/kubeconfig
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /config/kubeconfig
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /config/kubeconfig
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /config/kubeconfig
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /config/kubeconfig
Error: release v4m-prometheus-operator failed, and has been uninstalled due to atomic being set: timed out waiting for the condition
stderr_lines:
stdout: |-
INFO User directory: /tmp/ansible.78xfu5d4
INFO Helm client version: 3.9.4
INFO Kubernetes client version: v1.24.10
INFO Kubernetes server version: v1.24.14-eks-c12679a
namespace/monitoring created
serviceaccount/default patched
Deploying monitoring to the [monitoring] namespace...
INFO Adding [prometheus-community] helm repository
"prometheus-community" has been added to your repositories
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "prometheus-community" chart repository
Update Complete. ⎈Happy Helming!⎈
INFO Updating Prometheus Operator custom resource definitions
customresourcedefinition.apiextensions.k8s.io/alertmanagerconfigs.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/alertmanagers.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/prometheuses.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/prometheusrules.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/podmonitors.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/servicemonitors.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/thanosrulers.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/probes.monitoring.coreos.com created
No resources found
INFO Creating selfsigning-issuer for the [monitoring] namespace...
issuer.cert-manager.io/selfsigning-issuer created
INFO Creating self-signed CA certificate for the [monitoring] namespace...
certificate.cert-manager.io/ca-certificate created
INFO Creating namespace-issuer for the [monitoring] namespace...
issuer.cert-manager.io/namespace-issuer created
certificate.cert-manager.io/prometheus-tls-cert created
certificate.cert-manager.io/alertmanager-tls-cert created
certificate.cert-manager.io/grafana-tls-cert created
INFO Provisioning TLS-enabled Prometheus datasource for Grafana
configmap/grafana-datasource-prom-https created
configmap/grafana-datasource-prom-https labeled
INFO Enabling Prometheus node-exporter for TLS
configmap/node-exporter-tls-web-config created
configmap/node-exporter-tls-web-config labeled
INFO User response file: [/tmp/ansible.78xfu5d4/monitoring/user-values-prom-operator.yaml]
INFO Deploying the kube-prometheus stack. This may take a few minutes ...
INFO Installing via Helm (Tue Jun 27 07:20:06 UTC 2023 - timeout 20m)
Release "v4m-prometheus-operator" does not exist. Installing it now.
ERROR Exiting script [deploy_monitoring_cluster.sh] due to an error executing the command [helm $helmDebug upgrade --install $promRelease --namespace $MON_NS -f monitoring/values-prom-operator.yaml -f $istioValuesFile -f $tlsValuesFile -f $tlsPromAlertingEndpointFile -f $nodePortValuesFile -f $wnpValuesFile -f $PROM_OPER_USER_YAML --atomic --timeout 20m --set nameOverride=$promName --set fullnameOverride=$promName --set prometheus-node-exporter.fullnameOverride=$promName-node-exporter --set kube-state-metrics.fullnameOverride=$promName-kube-state-metrics --set grafana.fullnameOverride=$promName-grafana --set grafana.adminPassword="$grafanaPwd" --set prometheus.prometheusSpec.alertingEndpoints[0].namespace="$MON_NS" --version $KUBE_PROM_STACK_CHART_VERSION prometheus-community/kube-prometheus-stack].
stdout_lines:
Tuesday 27 June 2023 07:40:32 +0000 (0:21:46.930) 0:22:00.970 **
monitoring : cluster-monitoring - deploy --------------------------------------------------------------------------------------- 1306.93s
monitoring : v4m - download ------------------------------------------------------------------------------------------------------- 5.29s
monitoring : v4m - add storageclass ----------------------------------------------------------------------------------------------- 2.84s
monitoring : cluster-monitoring - lookup existing credentials --------------------------------------------------------------------- 1.46s
Gathering Facts ------------------------------------------------------------------------------------------------------------------- 0.75s
monitoring : cluster-monitoring - host-based user values -------------------------------------------------------------------------- 0.56s
monitoring : cluster-monitoring - create userdir ---------------------------------------------------------------------------------- 0.31s
global tmp dir -------------------------------------------------------------------------------------------------------------------- 0.28s
common role ----------------------------------------------------------------------------------------------------------------------- 0.07s
monitoring role - cluster --------------------------------------------------------------------------------------------------------- 0.05s
common : ansible.utils.update_fact ------------------------------------------------------------------------------------------------ 0.04s
common : migrations --------------------------------------------------------------------------------------------------------------- 0.04s
common : set_fact ----------------------------------------------------------------------------------------------------------------- 0.04s
monitoring : v4m - ensure supported value for V4M_ROUTING ------------------------------------------------------------------------- 0.04s
common : Load config file --------------------------------------------------------------------------------------------------------- 0.04s
common : task validation - ensure the onboard and offboard tasks are not run simultaneously --------------------------------------- 0.04s
common : task validation - ensure the other tasks run only with supported actions ------------------------------------------------- 0.04s
common : Set DEPLOY_DIR ----------------------------------------------------------------------------------------------------------- 0.04s
common : task validation - ensure the cas-onboard and offboard tasks are not run simultaneously ----------------------------------- 0.04s
common : Fail empty value --------------------------------------------------------------------------------------------------------- 0.04s
[app_user@KBPRECSVL0001 sasviya]$
Hi Team,
need your help, while running viya4-deployment --tags "cluster-logging,cluster-monitoring,viya-monitoring,install" command I am getting the following error message:
TASK [monitoring : cluster-monitoring - output credentials] ** ok: [localhost] => msg:
TASK [monitoring : cluster-monitoring - host-based user values] ** changed: [localhost] Tuesday 27 June 2023 07:18:45 +0000 (0:00:00.556) 0:00:13.974 ** Tuesday 27 June 2023 07:18:46 +0000 (0:00:00.032) 0:00:14.007 ** Tuesday 27 June 2023 07:18:46 +0000 (0:00:00.032) 0:00:14.039 **
TASK [monitoring : cluster-monitoring - deploy] ** fatal: [localhost]: FAILED! => changed=true cmd:
/tmp/ansible.78xfu5d4/viya4-monitoring-kubernetes/monitoring/bin/deploy_monitoring_cluster.sh delta: '0:21:46.604259' end: '2023-06-27 07:40:32.939904' msg: non-zero return code rc: 1 start: '2023-06-27 07:18:46.335645' stderr: |- Flag --short has been deprecated, and will be removed in the future. The --short output will become the default. Flag --short has been deprecated, and will be removed in the future. The --short output will become the default. WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /config/kubeconfig WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /config/kubeconfig WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /config/kubeconfig WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /config/kubeconfig WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /config/kubeconfig WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /config/kubeconfig WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /config/kubeconfig WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /config/kubeconfig Error: release v4m-prometheus-operator failed, and has been uninstalled due to atomic being set: timed out waiting for the condition stderr_lines:
stdout: |-
INFO User directory: /tmp/ansible.78xfu5d4
INFO Helm client version: 3.9.4
INFO Kubernetes client version: v1.24.10
INFO Kubernetes server version: v1.24.14-eks-c12679a
namespace/monitoring created serviceaccount/default patched Deploying monitoring to the [monitoring] namespace... INFO Adding [prometheus-community] helm repository "prometheus-community" has been added to your repositories Hang tight while we grab the latest from your chart repositories... ...Successfully got an update from the "prometheus-community" chart repository Update Complete. ⎈Happy Helming!⎈ INFO Updating Prometheus Operator custom resource definitions customresourcedefinition.apiextensions.k8s.io/alertmanagerconfigs.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/alertmanagers.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/prometheuses.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/prometheusrules.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/podmonitors.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/servicemonitors.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/thanosrulers.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/probes.monitoring.coreos.com created No resources found INFO Creating selfsigning-issuer for the [monitoring] namespace... issuer.cert-manager.io/selfsigning-issuer created INFO Creating self-signed CA certificate for the [monitoring] namespace... certificate.cert-manager.io/ca-certificate created INFO Creating namespace-issuer for the [monitoring] namespace... issuer.cert-manager.io/namespace-issuer created certificate.cert-manager.io/prometheus-tls-cert created certificate.cert-manager.io/alertmanager-tls-cert created certificate.cert-manager.io/grafana-tls-cert created INFO Provisioning TLS-enabled Prometheus datasource for Grafana configmap/grafana-datasource-prom-https created configmap/grafana-datasource-prom-https labeled INFO Enabling Prometheus node-exporter for TLS configmap/node-exporter-tls-web-config created configmap/node-exporter-tls-web-config labeled INFO User response file: [/tmp/ansible.78xfu5d4/monitoring/user-values-prom-operator.yaml] INFO Deploying the kube-prometheus stack. This may take a few minutes ... INFO Installing via Helm (Tue Jun 27 07:20:06 UTC 2023 - timeout 20m) Release "v4m-prometheus-operator" does not exist. Installing it now. ERROR Exiting script [deploy_monitoring_cluster.sh] due to an error executing the command [helm $helmDebug upgrade --install $promRelease --namespace $MON_NS -f monitoring/values-prom-operator.yaml -f $istioValuesFile -f $tlsValuesFile -f $tlsPromAlertingEndpointFile -f $nodePortValuesFile -f $wnpValuesFile -f $PROM_OPER_USER_YAML --atomic --timeout 20m --set nameOverride=$promName --set fullnameOverride=$promName --set prometheus-node-exporter.fullnameOverride=$promName-node-exporter --set kube-state-metrics.fullnameOverride=$promName-kube-state-metrics --set grafana.fullnameOverride=$promName-grafana --set grafana.adminPassword="$grafanaPwd" --set prometheus.prometheusSpec.alertingEndpoints[0].namespace="$MON_NS" --version $KUBE_PROM_STACK_CHART_VERSION prometheus-community/kube-prometheus-stack]. stdout_lines:
PLAY RECAP *** localhost : ok=23 changed=6 unreachable=0 failed=1 skipped=57 rescued=0 ignored=0
Tuesday 27 June 2023 07:40:32 +0000 (0:21:46.930) 0:22:00.970 **
monitoring : cluster-monitoring - deploy --------------------------------------------------------------------------------------- 1306.93s monitoring : v4m - download ------------------------------------------------------------------------------------------------------- 5.29s monitoring : v4m - add storageclass ----------------------------------------------------------------------------------------------- 2.84s monitoring : cluster-monitoring - lookup existing credentials --------------------------------------------------------------------- 1.46s Gathering Facts ------------------------------------------------------------------------------------------------------------------- 0.75s monitoring : cluster-monitoring - host-based user values -------------------------------------------------------------------------- 0.56s monitoring : cluster-monitoring - create userdir ---------------------------------------------------------------------------------- 0.31s global tmp dir -------------------------------------------------------------------------------------------------------------------- 0.28s common role ----------------------------------------------------------------------------------------------------------------------- 0.07s monitoring role - cluster --------------------------------------------------------------------------------------------------------- 0.05s common : ansible.utils.update_fact ------------------------------------------------------------------------------------------------ 0.04s common : migrations --------------------------------------------------------------------------------------------------------------- 0.04s common : set_fact ----------------------------------------------------------------------------------------------------------------- 0.04s monitoring : v4m - ensure supported value for V4M_ROUTING ------------------------------------------------------------------------- 0.04s common : Load config file --------------------------------------------------------------------------------------------------------- 0.04s common : task validation - ensure the onboard and offboard tasks are not run simultaneously --------------------------------------- 0.04s common : task validation - ensure the other tasks run only with supported actions ------------------------------------------------- 0.04s common : Set DEPLOY_DIR ----------------------------------------------------------------------------------------------------------- 0.04s common : task validation - ensure the cas-onboard and offboard tasks are not run simultaneously ----------------------------------- 0.04s common : Fail empty value --------------------------------------------------------------------------------------------------------- 0.04s [app_user@KBPRECSVL0001 sasviya]$
Kindly help.