Kubernetes：部署生成是35，但最新观察的一代为34
我有一个牧场主的kubernetes群集运行，我的包含七杆豆荚的应用程序正在运行为舵图。当我想更新应用程序时，我更新了容器映像并重新部署了吊舱。自3年以来，这效果很好。突然，当我尝试重新部署前端吊舱时，我会从牧场主GUI中收到以下错误消息：
部署生成是35，但最新观察的一代是34
我搜索了错误和“部署生成”，但是遇到这个问题似乎是Umcommon。 Google几乎没有结果，这让我感到奇怪……POD目前没有部署。
是否有人暗示为什么突然发生这种情况以及如何解决？
预先感谢
Ben
I have a Rancher Kubernetes Cluster running and my application containing sevral pods is running as a helm chart. When I wanted to update my application, I updated my container image and redeployed the pod. Since 3 years, this worked well. Suddenly, when I try to redeploy my frontend pod, I get the following error message from the rancher gui:
Deployment generation is 35, but latest observed generation is 34
I googled the error and "deployment generation", but it seems umcommon to have this problem. There are almost no results from google, what makes me wonder...The pod is not getting deployed currently.
Does anyone has a hint on why this suddenly happens and how to fix that?
Thanks in advance,
Ben
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
只需要暂停并重新部署部署。
由于部署的连续故障，由于该应用程序的内部错误（如数据库正在下降）或其他是内部服务器错误，因此尝试处于运行状态。
Just need to pause and redeploy the deployment.
It was due to consecutive failures of the deployment to try to be at a running state due to so internal errors of the app like the database being down or something else which was an internal server error.
这可能是由于失败或不完整的舵机升级等引起的。
是否可能解决问题的解决方案：
helm ls -n＆lt;Helm History＆lt; Chart-name＆gt; -n＆lt;命名空间＆gt;- 列出了过去的Helm修订版helm rollback＆lt; Chart; Chart-name＆gt; ＆lt;修订版＆gt; -n＆lt;命名空间＆gt;。以上应将您的图表恢复到较早的工作版本，并可能清除此错误。至少这对我有用。
This might have been caused by a failed or incomplete helm upgrade etc.
possible solution to your issue:
helm ls -n <namespace>helm history <chart-name> -n <namespace>- lists the past helm revisionshelm rollback <chart-name> <revision-version> -n <namespace>.The above should revert back your chart to an earlier working version and possibly clear this error. Atleast this worked for me.
我不知道这一点的确切解决方案，但是我必须重新启动整个集群以摆脱此消息并恢复部署能力。似乎真的很奇怪。
I don't know the exact solution to this, but I had to reboot the whole cluster to get rid of this message and regain the ability to deploy. Seems to be something really odd.