舵图部署活动性和就绪性失败错误

分类：编程问答

如何解决舵图部署活动性和就绪性失败错误

我有一个Openshift集群。我创建了一个自定义应用程序，并尝试使用Helm图表进行部署。当我使用“ oc new-app ”将其部署在Openshift上时，部署工作正常。但是当我使用头盔图部署它时，它不起作用。

以下是' oc get all '----

的输出 
[root@worker2 ~]#
[root@worker2 ~]# oc get all
NAME                                       READY   STATUS             RESTARTS   AGE
pod/chart-acme-85648d4645-7msdl            1/1     Running            0          3d7h
pod/chart1-acme-f8b65b78d-k2fb6            1/1     Running            0          3d7h
pod/netshoot                               1/1     Running            0          3d10h
pod/sample1-buildachart-5b5d9d8649-qqmsf   0/1     CrashLoopBackOff   672        2d9h
pod/sample2-686bb7f969-fx5bk               0/1     CrashLoopBackOff   674        2d9h
pod/vjobs-npm-96b65fcb-b2p27               0/1     CrashLoopBackOff   817        47h

NAME                          TYPE           CLUSTER-IP       EXTERNAL-IP   PORT(S)        AGE
service/chart-acme            LoadBalancer   172.30.174.208   <pending>     80:30222/TCP   3d7h
service/chart1-acme           LoadBalancer   172.30.153.36    <pending>     80:30383/TCP   3d7h
service/sample1-buildachart   NodePort       172.30.29.124    <none>        80:32375/TCP   2d9h
service/sample2               NodePort       172.30.19.24     <none>        80:32647/TCP   2d9h
service/vjobs-npm             NodePort       172.30.205.30    <none>        80:30476/TCP   47h

NAME                                  READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/chart-acme            1/1     1            1           3d7h
deployment.apps/chart1-acme           1/1     1            1           3d7h
deployment.apps/sample1-buildachart   0/1     1            0           2d9h
deployment.apps/sample2               0/1     1            0           2d9h
deployment.apps/vjobs-npm             0/1     1            0           47h

NAME                                             DESIRED   CURRENT   READY   AGE
replicaset.apps/chart-acme-85648d4645            1         1         1       3d7h
replicaset.apps/chart1-acme-f8b65b78d            1         1         1       3d7h
replicaset.apps/sample1-buildachart-5b5d9d8649   1         1         0       2d9h
replicaset.apps/sample2-686bb7f969               1         1         0       2d9h
replicaset.apps/vjobs-npm-96b65fcb               1         1         0       47h
[root@worker2 ~]#
[root@worker2 ~]#

根据上图，您可以看到部署“ vjobs-npm ”给出了“ CrashLoopBackOff ”错误。

下面是“ oc describe pod ”的输出---- 

[root@worker2 ~]#
[root@worker2 ~]# oc describe pod vjobs-npm-96b65fcb-b2p27
Name:         vjobs-npm-96b65fcb-b2p27
Namespace:    vjobs-testing
Priority:     0
Node:         worker0/192.168.100.109
Start Time:   Mon,31 Aug 2020 09:30:28 -0400
Labels:       app.kubernetes.io/instance=vjobs-npm
              app.kubernetes.io/name=vjobs-npm
              pod-template-hash=96b65fcb
Annotations:  openshift.io/scc: restricted
Status:       Running
IP:           10.131.0.107
IPs:
  IP:           10.131.0.107
Controlled By:  ReplicaSet/vjobs-npm-96b65fcb
Containers:
  vjobs-npm:
    Container ID:   cri-o://c232849eb25bd96ae9343ac3ed1539d492985dd8cdf47a5a4df7d3cf776c4cf3
    Image:          quay.io/aditya7002/vjobs_local_build_new:latest
    Image ID:       quay.io/aditya7002/vjobs_local_build_new@sha256:87f18e3a24fc7043a43a143e96b0b069db418ace027d95a5427cf53de56feb4c
    Port:           80/TCP
    Host Port:      0/TCP
    State:          Running
      Started:      Mon,31 Aug 2020 09:31:23 -0400
    Last State:     Terminated
      Reason:       Error
      Exit Code:    137
      Started:      Mon,31 Aug 2020 09:30:31 -0400
      Finished:     Mon,31 Aug 2020 09:31:22 -0400
    Ready:          False
    Restart Count:  1
    Liveness:       http-get http://:http/ delay=0s timeout=1s period=10s #success=1 #failure=3
    Readiness:      http-get http://:http/ delay=0s timeout=1s period=10s #success=1 #failure=3
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from vjobs-npm-token-vw6f7 (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  vjobs-npm-token-vw6f7:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  vjobs-npm-token-vw6f7
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason     Age                From               Message
  ----     ------     ----               ----               -------
  Normal   Scheduled  68s                default-scheduler  Successfully assigned vjobs-testing/vjobs-npm-96b65fcb-b2p27 to worker0
  Normal   Killing    44s                kubelet,worker0   Container vjobs-npm failed liveness probe,will be restarted
  Normal   Pulling    14s (x2 over 66s)  kubelet,worker0   Pulling image "quay.io/aditya7002/vjobs_local_build_new:latest"
  Normal   Pulled     13s (x2 over 65s)  kubelet,worker0   Successfully pulled image "quay.io/aditya7002/vjobs_local_build_new:latest"
  Normal   Created    13s (x2 over 65s)  kubelet,worker0   Created container vjobs-npm
  Normal   Started    13s (x2 over 65s)  kubelet,worker0   Started container vjobs-npm
  Warning  Unhealthy  4s (x4 over 64s)   kubelet,worker0   Liveness probe failed: Get http://10.131.0.107:80/: dial tcp 10.131.0.107:80:
 connect: connection refused
  Warning  Unhealthy  1s (x7 over 61s)   kubelet,worker0   Readiness probe failed: Get http://10.131.0.107:80/: dial tcp 10.131.0.107:80
: connect: connection refused
[root@worker2 ~]#

版权声明：本文内容由互联网用户自发贡献，该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容， 请发送邮件至 dio@foxmail.com 举报，一经查实，本站将立刻删除。

相关推荐

导入项目后报错问题
依赖报错 idea导入项目后依赖报错，解决方案：https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错：更换其他版本 无法下载依赖可参考：https://blog.csdn.net/weixin_42628809/a
idea不能识别yaml文件
使用mybatis plus常见错误
错误1：代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
gradle常见问题与错误
错误1：gradle项目控制台输出为乱码 # 解决方案：https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
Mybatis Plus传入参数0不起作用
错误还原：在查询的过程中，传入的workType为0时，该条件不起作用 &lt;select id=&quot;xxx&quot;&gt; SELECT di.id, di.name, di.work_type, di.updated... &lt;where&gt; &lt;if test=&qu
linux中make编译源码包失败
报错如下，gcc版本太低 ^ server.c:5346:31: 错误：‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
微服务启动错误：Command line is too long. Shorten command line for
解决方案1 1、改项目中.idea/workspace.xml配置文件，增加dynamic.classpath参数 2、搜索PropertiesComponent，添加如下 &lt;property name=&quot;dynamic.classpath&quot; value=&quot;tru
vue常见错误
删除根组件app.vue中的默认代码后报错：Module Error (from ./node_modules/eslint-loader/index.js): 解决方案：关闭ESlint代码检测，在项目根目录创建vue.config.js，在文件中添加 module.exports = { lin
spark常见错误
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
matplotlib报错：AttributeError: module 'backend_interagg' has no attribute 'FigureCanvas'. Did you mean: 'FigureCanvasAgg'?
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams[&#39;font.sans-serif&#39;] = [&#39;SimHei&#39;] # 能正确显示负号 p
gitlab登录失败，报错：This challenge page was accidentally cached by an intermediary and is no longer available.
设置时间 控制面板
后端开发常见错误
错误1：Request method ‘DELETE‘ not supported 错误还原：controller层有一个接口，访问该接口时报错：Request method ‘DELETE‘ not supported 错误原因：没有接收到前端传入的参数，修改为如下 参考 错误2：cannot r
docker常见错误
错误1：启动docker镜像时报错：Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法：重启docker -&gt; systemctl r
idea常见错误
错误1：private field ‘xxx‘ is never assigned 按Altʾnter快捷键，选择第2项 参考：https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2：启动时报错，不能找到主启动类 #
pip安装依赖失败
报错如下，通过源不能下载，最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
maven常见错误
错误1：maven打包报错 错误还原：使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
cloud项目中常见错误
错误1：服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping(&quot;/hires&quot;) public class FeignControl
springboot常见错误
错误1：运行项目后报如下错误 解决方案 报错2：Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案：在pom.
springmvc拦截器中使用redisTemplate报空指针异常
参考 错误原因 过滤器或拦截器在生效时，redisTemplate还没有注入 解决方案：在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate&lt;String
vite报错：npm ERR! command C:WINDOWSsystem32cmd.exe /d /s /c C:UsersychenAppDataLocalTempnpx-dde1c848.cmd
使用vite构建项目报错 C:\Users\ychen\work&gt;npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-
pythonJavaScriptjavaHTMLPHPreactjsC#AndroidCSSNode.jssqlrpython-3.xMysqLjQueryc++pandasFlutterangularIOSdjangolinuxswifttypescript路由器JSON路由器设置无线路由器h3c华三华三路由器设置华三路由器电脑软件教程arraysdocker软件图文教程Cvue.jslaravelspring-boot