4.1.2安装devops 集群 Agent 报错

wenpengfan

创建部署问题时，请参考下面模板，你提供的信息越多，越容易及时获得解答。
发帖前请点击发表主题右边的预览(👀) 按钮，确保帖子格式正确。
你只花一分钟创建的问题，不能指望别人花上半个小时给你解答。

操作系统信息
虚拟机，Centos7.，16C/32G * 3

Kubernetes版本信息
例如：v1.31.0。3节点。

容器运行时
containerd，版本1.6.22

KubeSphere版本信息
v4.1.2。在线安装。全套安装。

问题是什么
安装devops报错

报错信息：

2024-10-31T17:13:57.888938803+08:00 Error: Get “https://10.211.0.1:443/api/v1/namespaces/argocd/services/devops-agent-argocd-repo-server”: dial tcp 10.211.0.1:443: connect: connection refused

2024-10-31T17:13:57.889034935+08:00 helm.go:84: [debug] Get “https://10.211.0.1:443/api/v1/namespaces/argocd/services/devops-agent-argocd-repo-server”: dial tcp 10.211.0.1:443: connect: connection refused

wenpengfan

argocd和Jenkins部署都是成功的，访问页面也没问题，但是因为上面agent的报错导致devops使用不了

wenpengfan

2024-11-01T14:27:16.634541258+08:00 Error: Get “https://10.211.0.1:443/api/v1/namespaces/argocd/services/devops-agent-argocd-repo-server”: dial tcp 10.211.0.1:443: connect: connection refused - error from a previous attempt: http2: server sent GOAWAY and closed the connection; LastStreamID=1961, ErrCode=NO_ERROR, debug=""

2024-11-01T14:27:16.634657666+08:00 helm.go:84: [debug] Get “https://10.211.0.1:443/api/v1/namespaces/argocd/services/devops-agent-argocd-repo-server”: dial tcp 10.211.0.1:443: connect: connection refused - error from a previous attempt: http2: server sent GOAWAY and closed the connection; LastStreamID=1961, ErrCode=NO_ERROR, debug=""

wenpengfan

重新运行这个任务报错：

2024-11-01T14:46:41.573531713+08:00 WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: kube.config

2024-11-01T14:46:41.573601428+08:00 WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: kube.config

2024-11-01T14:46:41.598947422+08:00 history.go:56: [debug] getting history for release devops-agent

2024-11-01T14:46:42.350201444+08:00 upgrade.go:155: [debug] preparing upgrade for devops-agent

2024-11-01T14:46:42.681432355+08:00 Error: UPGRADE FAILED: another operation (install/upgrade/rollback) is in progress

2024-11-01T14:46:42.681513867+08:00 helm.go:84: [debug] another operation (install/upgrade/rollback) is in progress

2024-11-01T14:46:42.681539322+08:00 helm.sh/helm/v3/pkg/action.init

2024-11-01T14:46:42.681559948+08:00 helm.sh/helm/v3/pkg/action/action.go:52

2024-11-01T14:46:42.681580350+08:00 runtime.doInit1

2024-11-01T14:46:42.681627968+08:00 runtime/proc.go:6735

2024-11-01T14:46:42.681647336+08:00 runtime.doInit

2024-11-01T14:46:42.681696425+08:00 runtime/proc.go:6702

2024-11-01T14:46:42.681729478+08:00 runtime.main

2024-11-01T14:46:42.681745982+08:00 runtime/proc.go:249

2024-11-01T14:46:42.681760621+08:00 runtime.goexit

2024-11-01T14:46:42.681774903+08:00 runtime/asm_amd64.s:1650

2024-11-01T14:46:42.681788437+08:00 UPGRADE FAILED

2024-11-01T14:46:42.681803309+08:00 main.newUpgradeCmd.func2

2024-11-01T14:46:42.681817144+08:00 helm.sh/helm/v3/cmd/helm/upgrade.go:229

2024-11-01T14:46:42.681830576+08:00 github.com/spf13/cobra.(*Command).execute

2024-11-01T14:46:42.681845488+08:00 github.com/spf13/cobra@v1.8.0/command.go:983

2024-11-01T14:46:42.681862769+08:00 github.com/spf13/cobra.(*Command).ExecuteC

2024-11-01T14:46:42.681880411+08:00 github.com/spf13/cobra@v1.8.0/command.go:1115

2024-11-01T14:46:42.681895093+08:00 github.com/spf13/cobra.(*Command).Execute

2024-11-01T14:46:42.681908660+08:00 github.com/spf13/cobra@v1.8.0/command.go:1039

2024-11-01T14:46:42.681922206+08:00 main.main

2024-11-01T14:46:42.681935909+08:00 helm.sh/helm/v3/cmd/helm/helm.go:83

2024-11-01T14:46:42.681949478+08:00 runtime.main

2024-11-01T14:46:42.681966315+08:00 runtime/proc.go:267

2024-11-01T14:46:42.681984208+08:00 runtime.goexit

2024-11-01T14:46:42.682003073+08:00 runtime/asm_amd64.s:1650

pky

我也是

yudong

pky 是同样的报错吗？看下 devops-jenkins pod 的状态呢；

pky

yudong 我看了是启动探针和就绪探针不行，我尝试延长探针等待时间，也不行。后来直接在yaml里删除探针，发现启动jenkins容器是没成功的：容器内部的日志到这里就结束了：

我怎么都记得jenkins启动日志老长了，不是只有这么一点点啊

yudong

pky 如果只有这点日志，jenkins 应该还没有启动；看下是不是 devops-jenkins 资源配置的太少了。

pky

yudong 命令执行到解压缩war包的时候很慢，长达几分钟，而探针检测机制直接让其重启，也就是说还没来得及对外提供服务就被探针重启了。我的建议是延长探针时间或者修改检测方式。