操作系统信息
物理机,ubuntu 20.04,40C366G
Kubernetes版本信息
1.23.12
容器运行时
将 docker version
20.10.12
KubeSphere版本信息
在已有k8s集群上,在线安装 3.3.1版本
问题是什么
告警页面无法进入,报thanoruler未安装,我反复安装卸载了多次,都不行。
安装,命令类似 kubectl apply -f installer.yaml、kubectl apply -f configuration.yaml、kubectl apply -f bundle.yaml。
卸载使用kubesphere-delete.sh。
task monitoring status is failed (8/8)
**************************************************
Collecting installation results …
Task ‘monitoring’ failed:
******************************************************************************************************************************************************
{
“counter”: 143,
“created”: “2022-11-24T02:15:49.304178”,
“end_line”: 136,
“event”: “runner_on_failed”,
“event_data”: {
"duration": 54.189537,
"end": "2022-11-24T02:15:49.303905",
"event_loop": null,
"host": "localhost",
"ignore_errors": null,
"play": "localhost",
"play_pattern": "localhost",
"play_uuid": "4656ef95-71b7-80a2-2e69-000000000005",
"playbook": "/kubesphere/playbooks/monitoring.yaml",
"playbook_uuid": "85968e55-7766-4d8f-9635-f880abd223df",
"remote_addr": "127.0.0.1",
"res": {
"_ansible_no_log": false,
"attempts": 3,
"changed": true,
"cmd": "/usr/local/bin/helm upgrade --install notification-manager /kubesphere/kubesphere/notification-manager -f /kubesphere/kubesphere/notification-manager/custom-values-notification.yaml -n kubesphere-monitoring-system --force\\n",
"delta": "0:00:05.776073",
"end": "2022-11-24 10:15:49.281251",
"invocation": {
"module_args": {
"_raw_params": "/usr/local/bin/helm upgrade --install notification-manager /kubesphere/kubesphere/notification-manager -f /kubesphere/kubesphere/notification-manager/custom-values-notification.yaml -n kubesphere-monitoring-system --force\\n",
"_uses_shell": true,
"argv": null,
"chdir": null,
"creates": null,
"executable": null,
"removes": null,
"stdin": null,
"stdin_add_newline": true,
"strip_empty_ends": true,
"warn": true
}
},
"msg": "non-zero return code",
"rc": 1,
"start": "2022-11-24 10:15:43.505178",
"stderr": "Error: rendered manifests contain a resource that already exists. Unable to continue with install: ServiceAccount \\"notification-manager-sa\\" in namespace \\"kubesphere-monitoring-system\\" exists and cannot be imported into the current release: invalid ownership metadata; label validationerror: missing key \\"app.kubernetes.io/managed-by\\": must be set to \\"Helm\\"; annotation validation error: missing key \\"meta.helm.sh/release-name\\": must be set to \\"notification-manager\\"; annotation validation error: missing key \\"meta.helm.sh/release-namespace\\": must be set to \\"kubesphere-monitoring-system\\"",
"stderr_lines": [
"Error: rendered manifests contain a resource that already exists. Unable to continue with install: ServiceAccount \\"notification-manager-sa\\" in namespace \\"kubesphere-monitoring-system\\" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key \\"app.kubernetes.io/managed-by\\": must be set to \\"Helm\\"; annotation validation error: missing key \\"meta.helm.sh/release-name\\": must be set to \\"notification-manager\\"; annotation validation error: missing key \\"meta.helm.sh/release-namespace\\": must be set to \\"kubesphere-monitoring-system\\""
],
"stdout": "Release \\"notification-manager\\" does not exist. Installing it now.",
"stdout_lines": [
"Release \\"notification-manager\\" does not exist. Installing it now."
]
},
"resolved_action": "command",
"role": "ks-monitor",
"start": "2022-11-24T02:14:55.114368",
"task": "notification-manager | Deploying notification-manager",
"task_action": "command",
"task_args": "",
"task_path": "/kubesphere/installer/roles/ks-monitor/tasks/notification-manager.yaml:36",
"task_uuid": "4656ef95-71b7-80a2-2e69-000000000057",
"uuid": "f7ab1c7b-610d-494f-9fea-fca06a03570b"
},
“parent_uuid”: “4656ef95-71b7-80a2-2e69-000000000057”,
“pid”: 5703,
“runner_ident”: “monitoring”,
“start_line”: 135,
“stdout”: "fatal: [localhost]: FAILED! => {\“attempts\”: 3, \“changed\”: true, \“cmd\”: \“/usr/local/bin/helm upgrade –install notification-manager /kubesphere/kubesphere/notification-manager -f /kubesphere/kubesphere/notification-manager/custom-values-notification.yaml -n kubesphere-monitoring-system–force\\n\”, \“delta\”: \“0:00:05.776073\”, \“end\”: \“2022-11-24 10:15:49.281251\”, \“msg\”: \“non-zero return code\”, \“rc\”: 1, \“start\”: \“2022-11-24 10:15:43.505178\”, \“stderr\”: \"Error: rendered manifests contain a resource that already exists. Unable to continue with install: ServiceAccount \\\“notification-manager-sa\\\” in namespace \\\“kubesphere-monitoring-system\\\” exists and cannot be imported into the current release: invalid ownershipmetadata; label validation error: missing key \\\“app.kubernetes.io/managed-by\\\”: must be set to \\\“Helm\\\”; annotation validation error: missing key \\\“meta.helm.sh/release-name\\\”: must be set to \\\“notification-manager\\\”; annotation validation error: missing key \\\“meta.helm.sh/release-namespace\\\”: must be set to \\\“kubesphere-monitoring-system\\\”\", \“stderr_lines\”: [\"Error: rendered manifests contain a resource that already exists. Unable to continue with install: ServiceAccount \\\“notification-manager-sa\\\” in namespace \\\“kubesphere-monitoring-system\\\” exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key \\\“app.kubernetes.io/managed-by\\\”: must be set to \\\“Helm\\\”; annotation validation error: missing key \\\“meta.helm.sh/release-name\\\”: must be set to \\\“notification-manager\\\”; annotation validation error: missing key \\\“meta.helm.sh/release-namespace\\\”: must be set to \\\“kubesphere-monitoring-system\\\”\"], \“stdout\”: \"Release \\\“notification-manager\\\” does not exist. Installing it now.\", \“stdout_lines\”: [\"Release \\\“notification-manager\\\” does not exist. Installing it now.\“]}”,
“uuid”: “f7ab1c7b-610d-494f-9fea-fca06a03570b”
}