question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Bug]: Helm deployment failure

See original GitHub issue

Preflight Checklist

  • I agree to follow the Code of Conduct that this project adheres to.
  • I have searched the issue tracker for an issue that matches the one I want to file, without success.
  • I am not looking for support or already pursued the available support channels without success.

Version

1.8.3

Installation Type

Official Kubernetes

Service Name

Deploy(DongTai-deploy)

Describe the details of the bug and the steps to reproduce it

Hello, Helm deployment failure, please help to analyze

Helm parameter helm install – create-namespace-n dongtai --set accessType=NodePort – values. /values.yaml dongtai-iast dongtai/dongtai-iast

values.yaml

# Default values for dongtai.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.

replicaCount: 1

# dongtai config
# appNamespace: dongtai-iast
skipMysql: true 
skipRedis: true
accessType: ClusterIP 
imageVersion: latest

mysql:
  host: mariadb-dddd.ddd
  port: 3306
  name: dongtai_webapi
  user: root
  password: ddddd!

redis:
  host: redis-dddd.ddd
  port: 6379
  password: ddddd!
  db: 0

enginUrl: http://dongtai-engine-svc:80

apiServer: http://dongtai-openapi-svc:80

csrfTrustOrigins: .example.com
secretKey: vbjlvbxfvazjfprywuxgyclmvhtmselddsefxxlcixovmqfpgy
smtp:
  server: smtp_server
  user: smtp_user
  password: smtp_password
  from_addr: from_addr
  ssl: False
  cc_addr: cc_addr

aliyun_oss:
  access_key: LTAI5t7pu9WUT2DcbknfNiaD
  access_key_secret: ZoEOSi7KfayQ7JalvJVHa37fdZ4XFY

sca:
  base_url: https://iast.uuu.com
storageClassName:
  name: managed-nfs-storage  

Additional Information

image image

Logs

# dongtai-server
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
启动uwsgi服务
config file not exist. stop running
config file not exist. stop running

[uWSGI] getting INI configuration from /opt/dongtai/dongtai_conf/conf/uwsgi.ini
[uwsgi-static] added mapping for /upload => /opt/dongtai/static
*** Starting uWSGI 2.0.19.1 (64bit) on [Wed Aug 17 14:59:14 2022] ***
compiled with version: 10.2.1 20210110 on 05 August 2022 10:52:21
os: Linux-3.10.0-1160.el7.x86_64 #1 SMP Mon Oct 19 16:18:59 UTC 2020
nodename: dongtai-server-fcc995575-j4vsn
machine: x86_64
clock source: unix
detected number of CPU cores: 8
current working directory: /opt/dongtai
detected binary path: /usr/local/bin/uwsgi
!!! no internal routing support, rebuild with pcre support !!!
uWSGI running as root, you can use --uid/--gid/--chroot options
*** WARNING: you are running uWSGI as root !!! (use the --uid flag) *** 
chdir() to /opt/dongtai
your memory page size is 4096 bytes
detected max file descriptor number: 1048576
building mime-types dictionary from file /etc/mime.types...1476 entry found
lock engine: pthread robust mutexes
thunder lock: disabled (you can enable it with --thunder-lock)
Listen queue size is greater than the system max net.core.somaxconn (128).

# dongtai-engine-task
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
/bin/bash: /opt/dongtai/webapi/docker/entrypoint.sh: No such file or directory

# dongtai-engine
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
/bin/bash: /opt/dongtai/webapi/docker/entrypoint.sh: No such file or directory

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:5

github_iconTop GitHub Comments

1reaction
Changegocommented, Aug 18, 2022

Hello,Has it been fixed?

0reactions
Changegocommented, Aug 24, 2022

Hi. Are you sure it’s fixed?

I reverse install and clean up the image. A fresh install

helm install --create-namespace -n dongtai --set accessType=NodePort dongtai-iast dongtai/dongtai-iast --values ./values.yaml

It still seems to be unresolved.

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to Fix helm "has no deployed releases" Error - phoenixNAP
Fixing the “helm has no deployed releases” Error · Solution 1: Changing the Deployment Status · Solution 2: Cleaning Up Failed Deployments.
Read more >
How to fix Helm's "Upgrade Failed: has no deployed releases ...
To correct it, it's quite easy. You just need to update the last secret related to your release. In it, there is a...
Read more >
How to fix “Helm Upgrade Error: has no deployed releases ...
In fact, Helm only tries to filter out failed deployments by only looking at the STATUS field of the deployment history and report...
Read more >
How can I tell what causes a helm chart deployment to fail?
Helm chart deployment can fail because of the below 3 reasons. Chart is incorrect; Deployment configurations are incorrect.
Read more >
Helm is inconsistent about failed deployments #2437 - GitHub
It seems that helm does not care if for some unknown class of reasons a deployment fails. Helm will report the failure but...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found