jumpserver / helm-charts Goto Github PK

View Code? Open in Web Editor NEW

36.0 36.0 32.0 356 KB

Helm charts for JumpServer

License: GNU General Public License v3.0

Mustache 100.00%

helm-charts's People

Contributors

Stargazers

Watchers

helm-charts's Issues

[Bug] magnus默认端口映射问题

JumpServer 版本(v1.5.9以下不再支持)
3.10.3

浏览器版本

Bug 描述
在values.yaml配置了magnus service mysql端口号为32061
最后生成的yaml(我用的helm --dry-run)中,所有magnus Deployment中所有涉及mysql端口号都变成了32061,其他地方涉及到magnus mysql端口号的也都变成了32061,而.magnus容器的端口号本来是为33061.所以magnus组件就可用了.

Bug 重现步骤(有截图更好)
1.
2.
3.

[Bug] jumpserver-jms-celery一直在重启

JumpServer 版本(v1.5.9以下不再支持)

浏览器版本

Bug 描述
Liveness probe failed: OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "./jms status task | grep stopped && exit 1 || exit 0": stat ./jms status task | grep stopped && exit 1 || exit 0: no such file or directory: unknown

Bug 重现步骤(有截图更好)

[Question] 使用helm安装时出现如下问题running PreBind plugin "VolumeBinding":

请描述您的问题.
k8s version: v1.21.5
使用helm安装出现
running PreBind plugin "VolumeBinding": Operation cannot be fulfilled on persistentvolumeclaims "jumpser-0589ra-jumpserver-jms-core-data": the object has been modified; please apply your changes to the latest version and try again
然后一直等待直到超时

[Question] deployment jumpserver-jms-core 报错

报错如下：我该怎么解决？
2021-08-12T13:13:05.897336013Z 2021-08-12 21:13:05 Check database connection ...
2021-08-12T13:13:06.124980935Z Traceback (most recent call last):
2021-08-12T13:13:06.125005402Z File "manage.py", line 28, in
2021-08-12T13:13:06.125011563Z execute_from_command_line(sys.argv)
2021-08-12T13:13:06.125016209Z File "/usr/local/lib/python3.8/site-packages/django/core/management/init.py", line 401, in execute_from_command_line
2021-08-12T13:13:06.12502115Z utility.execute()
2021-08-12T13:13:06.125025558Z File "/usr/local/lib/python3.8/site-packages/django/core/management/init.py", line 395, in execute
2021-08-12T13:13:06.125030106Z self.fetch_command(subcommand).run_from_argv(self.argv)
2021-08-12T13:13:06.125034206Z File "/usr/local/lib/python3.8/site-packages/django/core/management/base.py", line 330, in run_from_argv
2021-08-12T13:13:06.125038563Z self.execute(*args, **cmd_options)
2021-08-12T13:13:06.125042601Z File "/usr/local/lib/python3.8/site-packages/django/core/management/base.py", line 368, in execute
2021-08-12T13:13:06.125046942Z self.check()
2021-08-12T13:13:06.125050962Z File "/usr/local/lib/python3.8/site-packages/django/core/management/base.py", line 392, in check
2021-08-12T13:13:06.125055623Z all_issues = checks.run_checks(
2021-08-12T13:13:06.125059891Z File "/usr/local/lib/python3.8/site-packages/django/core/checks/registry.py", line 70, in run_checks
2021-08-12T13:13:06.125064483Z new_errors = check(app_configs=app_configs, databases=databases)
2021-08-12T13:13:06.125068879Z File "/usr/local/lib/python3.8/site-packages/django/core/checks/model_checks.py", line 18, in check_all_models
2021-08-12T13:13:06.125073584Z models = apps.get_models()
2021-08-12T13:13:06.125077951Z File "/usr/local/lib/python3.8/site-packages/django/apps/registry.py", line 179, in get_models
2021-08-12T13:13:06.125082464Z self.check_models_ready()
2021-08-12T13:13:06.125086683Z File "/usr/local/lib/python3.8/site-packages/django/apps/registry.py", line 141, in check_models_ready
2021-08-12T13:13:06.125102222Z raise AppRegistryNotReady("Models aren't loaded yet.")
2021-08-12T13:13:06.125106898Z django.core.exceptions.AppRegistryNotReady: Models aren't loaded yet.

[Question] helm部署core组件一直启动不起来

请描述您的问题.
您好，我使用helm部署jumpserver发现core组件一直启动不成功（估计是指针超时重启），导致其他组件连接不上core也一直在重启。core日志开启debug模式也无报错信息。

NAME                               READY   STATUS    RESTARTS   AGE
jump-jms-celery-64c7f59f8f-sj6q5   1/1     Running   0          13m
jump-jms-core-59bdf5fc-r8lg6       0/1     Running   1          13m
jump-jms-koko-6f87fdd947-vlm5s     0/1     Running   2          13m
jump-jms-lion-6c4c58d5b9-b5l42     0/1     Running   2          13m
jump-jms-web-fd777d4ff-4d5l5       0/1     Running   2          13m
jumpserver-mysql-0                 1/1     Running   0          2d4h
redis-master-0                     1/1     Running   0          46h

core日志

# kubectl logs -f -n jumpserver jump-jms-core-59bdf5fc-r8lg6 
2022-06-24 15:19:07 [common DEBUG] Start subscribe for expire orgs mapping from memory
2022-06-24 15:19:07 [node_assets_mapping DEBUG] Start subscribe for expire node assets id mapping from memory
2022-06-24 15:19:11 [signals_handler DEBUG] Start subscribe setting change
2022-06-24 15:19:11 Check database connection: 0
2022-06-24 15:19:12 Database connect success
2022-06-24 15:19:12 Collect static files
2022-06-24 15:19:13 Collect static files done
2022-06-24 15:19:13 Check database structure change ...
2022-06-24 15:19:13 Migrate model change to database ...
2022-06-24 15:19:14 Fri Jun 24 15:19:14 2022
2022-06-24 15:19:14 JumpServer version v2.19.0, more see https://www.jumpserver.org

进入pod内部，查询beat.log日志：

/usr/local/lib/python3.8/site-packages/jmespath/visitor.py:32: SyntaxWarning: "is" with a literal. Did you mean "=="?
  if x is 0 or x is 1:
/usr/local/lib/python3.8/site-packages/jmespath/visitor.py:32: SyntaxWarning: "is" with a literal. Did you mean "=="?
  if x is 0 or x is 1:
/usr/local/lib/python3.8/site-packages/jmespath/visitor.py:34: SyntaxWarning: "is" with a literal. Did you mean "=="?
  elif y is 0 or y is 1:
/usr/local/lib/python3.8/site-packages/jmespath/visitor.py:34: SyntaxWarning: "is" with a literal. Did you mean "=="?
  elif y is 0 or y is 1:
/usr/local/lib/python3.8/site-packages/jmespath/visitor.py:260: SyntaxWarning: "is" with a literal. Did you mean "=="?
  if original_result is 0:
2022-06-24 16:28:08 [common DEBUG] Start subscribe for expire orgs mapping from memory
2022-06-24 16:28:08 [node_assets_mapping DEBUG] Start subscribe for expire node assets id mapping from memory
2022-06-24 16:28:12 [signals_handler DEBUG] Start subscribe setting change
beat: Starting...
Writing entries...
Writing entries...
Writing entries...
Writing entries...
Writing entries...
~

celery_ansible.log:

/usr/local/lib/python3.8/site-packages/jmespath/visitor.py:32: SyntaxWarning: "is" with a literal. Did you mean "=="?
  if x is 0 or x is 1:
/usr/local/lib/python3.8/site-packages/jmespath/visitor.py:32: SyntaxWarning: "is" with a literal. Did you mean "=="?
  if x is 0 or x is 1:
/usr/local/lib/python3.8/site-packages/jmespath/visitor.py:34: SyntaxWarning: "is" with a literal. Did you mean "=="?
  elif y is 0 or y is 1:
/usr/local/lib/python3.8/site-packages/jmespath/visitor.py:34: SyntaxWarning: "is" with a literal. Did you mean "=="?
  elif y is 0 or y is 1:
/usr/local/lib/python3.8/site-packages/jmespath/visitor.py:260: SyntaxWarning: "is" with a literal. Did you mean "=="?
  if original_result is 0:
/usr/local/lib/python3.8/site-packages/azure/storage/blob/_upload_chunking.py:403: SyntaxWarning: "is" with a literal. Did you mean "=="?
  if n is 0 or self._buffer.closed:
/usr/local/lib/python3.8/site-packages/azure/storage/blob/baseblobservice.py:1008: SyntaxWarning: "is not" with a literal. Did you mean "!="?
  if lease_duration is not -1 and \
/usr/local/lib/python3.8/site-packages/azure/storage/blob/baseblobservice.py:2607: SyntaxWarning: "is not" with a literal. Did you mean "!="?
  if lease_duration is not -1 and \
/usr/local/lib/python3.8/site-packages/azure/storage/common/_connection.py:82: SyntaxWarning: "is" with a literal. Did you mean "=="?
  self.protocol = self.protocol if parsed_url.scheme is '' else parsed_url.scheme
2022-06-24 16:28:08 [common DEBUG] Start subscribe for expire orgs mapping from memory
2022-06-24 16:28:08 [node_assets_mapping DEBUG] Start subscribe for expire node assets id mapping from memory
2022-06-24 16:28:12 [signals_handler DEBUG] Start subscribe setting change
/usr/local/lib/python3.8/site-packages/celery/platforms.py:800: RuntimeWarning: You're running the worker with superuser privileges: this is
absolutely not recommended!

Please specify a different user using the --uid option.

User information: uid=0 euid=0 gid=0 egid=0

  warnings.warn(RuntimeWarning(ROOT_DISCOURAGED.format(
Connected to redis://:**@redis-headless:6379/3
mingle: searching for neighbors
mingle: all alone
/usr/local/lib/python3.8/site-packages/celery/fixups/django.py:202: UserWarning: Using settings.DEBUG leads to a memory
            leak, never use this setting in production environments!
  warnings.warn('''Using settings.DEBUG leads to a memory
ansible@jump-jms-celery-64c7f59f8f-7g55x ready.
Events of group {task} enabled by remote.

gunicorn.log:

[2022-06-24 16:37:53 +0800] [282] [INFO] Starting gunicorn 19.9.0
[2022-06-24 16:37:53 +0800] [282] [INFO] Listening at: http://0.0.0.0:8080 (282)
[2022-06-24 16:37:53 +0800] [282] [INFO] Using worker: gthread
/usr/local/lib/python3.8/os.py:1023: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used
  return io.open(fd, *args, **kwargs)
[2022-06-24 16:37:53 +0800] [285] [INFO] Booting worker with pid: 285
/usr/local/lib/python3.8/os.py:1023: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used
  return io.open(fd, *args, **kwargs)
[2022-06-24 16:37:53 +0800] [287] [INFO] Booting worker with pid: 287
/usr/local/lib/python3.8/os.py:1023: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used
  return io.open(fd, *args, **kwargs)
[2022-06-24 16:37:53 +0800] [289] [INFO] Booting worker with pid: 289
/usr/local/lib/python3.8/os.py:1023: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used
  return io.open(fd, *args, **kwargs)
[2022-06-24 16:37:53 +0800] [291] [INFO] Booting worker with pid: 291
2022-06-24 16:37:56 [common DEBUG] Start subscribe for expire orgs mapping from memory
2022-06-24 16:37:56 [node_assets_mapping DEBUG] Start subscribe for expire node assets id mapping from memory
2022-06-24 16:37:57 [common DEBUG] Start subscribe for expire orgs mapping from memory
2022-06-24 16:37:57 [node_assets_mapping DEBUG] Start subscribe for expire node assets id mapping from memory
2022-06-24 16:37:57 [common DEBUG] Start subscribe for expire orgs mapping from memory
2022-06-24 16:37:57 [node_assets_mapping DEBUG] Start subscribe for expire node assets id mapping from memory
2022-06-24 16:37:57 [common DEBUG] Start subscribe for expire orgs mapping from memory
2022-06-24 16:37:57 [node_assets_mapping DEBUG] Start subscribe for expire node assets id mapping from memory
2022-06-24 16:38:00 [signals_handler DEBUG] Start subscribe setting change
2022-06-24 16:38:00 [base DEBUG] MiddlewareNotUsed: 'authentication.backends.cas.middleware.CASMiddleware'
2022-06-24 16:38:01 [signals_handler DEBUG] Start subscribe setting change
2022-06-24 16:38:01 [base DEBUG] MiddlewareNotUsed: 'authentication.backends.cas.middleware.CASMiddleware'
2022-06-24 16:38:01 [base DEBUG] MiddlewareNotUsed: 'authentication.backends.oidc.middleware.OIDCRefreshIDTokenMiddleware'
2022-06-24 16:38:01 [base DEBUG] MiddlewareNotUsed: 'jumpserver.middleware.RefererCheckMiddleware'
2022-06-24 16:38:01 [signals_handler DEBUG] Start subscribe setting change
2022-06-24 16:38:01 [base DEBUG] MiddlewareNotUsed: 'authentication.backends.cas.middleware.CASMiddleware'
2022-06-24 16:38:01 [signals_handler DEBUG] Start subscribe setting change
2022-06-24 16:38:01 [base DEBUG] MiddlewareNotUsed: 'authentication.backends.cas.middleware.CASMiddleware'
2022-06-24 16:38:01 [base DEBUG] MiddlewareNotUsed: 'authentication.backends.oidc.middleware.OIDCRefreshIDTokenMiddleware'
2022-06-24 16:38:01 [base DEBUG] MiddlewareNotUsed: 'jumpserver.middleware.RefererCheckMiddleware'
2022-06-24 16:38:01 [base DEBUG] MiddlewareNotUsed: 'authentication.backends.oidc.middleware.OIDCRefreshIDTokenMiddleware'
2022-06-24 16:38:01 [base DEBUG] MiddlewareNotUsed: 'jumpserver.middleware.RefererCheckMiddleware'
2022-06-24 16:38:01 [base DEBUG] MiddlewareNotUsed: 'authentication.backends.oidc.middleware.OIDCRefreshIDTokenMiddleware'
2022-06-24 16:38:01 [base DEBUG] MiddlewareNotUsed: 'jumpserver.middleware.RefererCheckMiddleware'

其它日志好像没有报错信息。

测试k8s集群无法连接外网，是否和网络有关系呢？

kubernetes版本：1.20.12
helm版本：v3.5.0
jumpserver helm-charts: 2.19.0

[Question] helm repo add 報錯

使用helm部署jumpserver報以下錯誤
helm repo add jumpserver https://jumpserver.github.io/helm-charts
Error: looks like "https://jumpserver.github.io/helm-charts" is not a valid chart repository or cannot be reached: Get "https://jumpserver.github.io/helm-charts/index.yaml": proxyconnect tcp: tls: first record does not look like a TLS handshake

[Question] Celery和Core的Pod使用相同的Label

请描述您的问题.
Chart里Celery使用了和Core相同的Pod.metadata.labels
https://github.com/jumpserver/helm-charts/blob/main/charts/jumpserver/templates/celery/deployment-celery.yaml#L25

同时Core的Service也是用的这部分Labels
https://github.com/jumpserver/helm-charts/blob/main/charts/jumpserver/templates/core/service-core.yaml#L31

这样的配置方法是有特殊用途吗？

[Bug] 组件kael有配置项决定启用还是禁用，但禁用后，web启动不了

JumpServer 版本(v1.5.9以下不再支持)
v3.5.2

浏览器版本
浏览器无关

Bug 描述
看文档介绍，kael是管理ChartGPT资源，因为没有这方面的需求，试着部署的时候将kael禁用掉(values.yaml当中，配置kael的enabled: false)，然后发现部署后唯独web所在pod启动失败，看错误信息，应该是找不到kael服务导致。既然允许配置，是不是不应该起不来啊？

Bug 重现步骤(有截图更好)

在values.yaml中配置kael的enabled: false
正常helm安装部署jumpserver
观察pod状态，可见web组件启动不了

[Question]

执行这条安装命令之后等一会儿会有以下报错，然后就停止运行了，helm install jumpserver1 ./
Error: failed pre-install: timed out waiting for the condition

[Question]

请描述您的问题.
使用helm安装后，在k8s job看到日志
The SECRET_KEY setting must not be empty

如何解决

[Question] K8S 应用没有客户端，KOKO 容器端应该如何解决？

请描述您的问题.
想知道 k8s 客户端的问题，目前 web console 打开以后提示没有客户端，应该是 koko 服务没有内置 kubectl？如果想增加支持应该如何操作？

[Bug] 登录日志的IP为局域网IP

JumpServer 版本(v1.5.9以下不再支持)
v3.8.2

浏览器版本
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36 |

Bug 描述
登录日志的IP为局域网IP，没有获取到用户的公网IP

Bug 重现步骤(有截图更好)

[Bug] 3.8.2升级到3.9.1失败，升级到3.9.0也不行，查看pod似乎是升级数据库失败

JumpServer 版本(v1.5.9以下不再支持)
v3.8.2

浏览器版本
浏览器无关

Bug 描述
helm方式，从3.8.2升级到3.9.1失败，就很长时间才提示超时。查看pod有多个升级数据库的pod处于err状态。logs pod看不到日志，就提示exec错误。已经恢复回3.8.2了，没法截图了。顺便，values.yaml中的镜像我已经从core改成core-ce了，不是镜像拉取不了的问题；也不是我升级不对的问题，一路从3.1左右跟着升级到3.8.2的，就这次不行。

Bug 重现步骤(有截图更好)
1.
2.
3.

[Bug]

JumpServer 版本(v1.5.9以下不再支持)
1.16.0

浏览器版本

Bug 描述

jumpserver-jms-init-db log:

2021-11-19 14:23:00 Collect static files
--
Fri, Nov 19 2021 2:23:00 pm | 2021-11-19 14:23:00 Collect static files done
Fri, Nov 19 2021 2:23:00 pm | 2021-11-19 14:23:00 Check database structure change ...
Fri, Nov 19 2021 2:23:00 pm | 2021-11-19 14:23:00 Migrate model change to database ...
Fri, Nov 19 2021 2:23:05 pm | 2021-11-19 14:23:05 [common DEBUG] Start subscribe for expire orgs mapping from memory
Fri, Nov 19 2021 2:23:05 pm | 2021-11-19 14:23:05 [node_assets_mapping DEBUG] Start subscribe for expire node assets id mapping from memory
Fri, Nov 19 2021 2:23:05 pm | 2021-11-19 14:23:05 [models DEBUG] Refresh setting: TERMINAL_HOST_KEY
Fri, Nov 19 2021 2:23:05 pm | 2021-11-19 14:23:05 [signals_handler DEBUG] Start subscribe setting change
Fri, Nov 19 2021 2:23:05 pm |  
Fri, Nov 19 2021 2:23:05 pm | 477 static files copied to '/opt/jumpserver/data/static'.
Fri, Nov 19 2021 2:23:07 pm | Operations to perform:
Fri, Nov 19 2021 2:23:07 pm | Apply all migrations: acls, admin, applications, assets, audits, auth, authentication, captcha, common, contenttypes, django_cas_ng, django_celery_beat, jms_oidc_rp, notifications, ops, orgs, perms, sessions, settings, terminal, tickets, users
Fri, Nov 19 2021 2:23:07 pm | Running migrations:
Fri, Nov 19 2021 2:23:07 pm | Traceback (most recent call last):
Fri, Nov 19 2021 2:23:07 pm | File "/usr/local/lib/python3.8/site-packages/django/db/backends/utils.py", line 84, in _execute
Fri, Nov 19 2021 2:23:07 pm | return self.cursor.execute(sql, params)
Fri, Nov 19 2021 2:23:07 pm | File "/usr/local/lib/python3.8/site-packages/django/db/backends/mysql/base.py", line 73, in execute
Fri, Nov 19 2021 2:23:07 pm | return self.cursor.execute(query, args)
Fri, Nov 19 2021 2:23:07 pm | File "/usr/local/lib/python3.8/site-packages/MySQLdb/cursors.py", line 206, in execute
Fri, Nov 19 2021 2:23:07 pm | res = self._query(query)
Fri, Nov 19 2021 2:23:07 pm | File "/usr/local/lib/python3.8/site-packages/MySQLdb/cursors.py", line 319, in _query
Fri, Nov 19 2021 2:23:07 pm | db.query(q)
Fri, Nov 19 2021 2:23:07 pm | File "/usr/local/lib/python3.8/site-packages/MySQLdb/connections.py", line 259, in query
Fri, Nov 19 2021 2:23:07 pm | _mysql.connection.query(self, query)
Fri, Nov 19 2021 2:23:07 pm | MySQLdb._exceptions.OperationalError: (1051, "Unknown table 'jumpserver.assets_asset_protocols'")
Fri, Nov 19 2021 2:23:07 pm |  
Fri, Nov 19 2021 2:23:07 pm | The above exception was the direct cause of the following exception:
Fri, Nov 19 2021 2:23:07 pm |  
Fri, Nov 19 2021 2:23:07 pm | Traceback (most recent call last):
Fri, Nov 19 2021 2:23:07 pm | File "manage.py", line 28, in <module>
Fri, Nov 19 2021 2:23:07 pm | execute_from_command_line(sys.argv)
Fri, Nov 19 2021 2:23:07 pm | File "/usr/local/lib/python3.8/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line
Fri, Nov 19 2021 2:23:07 pm | utility.execute()
Fri, Nov 19 2021 2:23:07 pm | File "/usr/local/lib/python3.8/site-packages/django/core/management/__init__.py", line 395, in execute
Fri, Nov 19 2021 2:23:07 pm | self.fetch_command(subcommand).run_from_argv(self.argv)
Fri, Nov 19 2021 2:23:07 pm | File "/usr/local/lib/python3.8/site-packages/django/core/management/base.py", line 330, in run_from_argv
Fri, Nov 19 2021 2:23:07 pm | self.execute(*args, **cmd_options)
Fri, Nov 19 2021 2:23:07 pm | File "/usr/local/lib/python3.8/site-packages/django/core/management/base.py", line 371, in execute
Fri, Nov 19 2021 2:23:07 pm | output = self.handle(*args, **options)
Fri, Nov 19 2021 2:23:07 pm | File "/usr/local/lib/python3.8/site-packages/django/core/management/base.py", line 85, in wrapped
Fri, Nov 19 2021 2:23:07 pm | res = handle_func(*args, **kwargs)
Fri, Nov 19 2021 2:23:07 pm | File "/usr/local/lib/python3.8/site-packages/django/core/management/commands/migrate.py", line 243, in handle
Fri, Nov 19 2021 2:23:07 pm | post_migrate_state = executor.migrate(
Fri, Nov 19 2021 2:23:07 pm | File "/usr/local/lib/python3.8/site-packages/django/db/migrations/executor.py", line 117, in migrate
Fri, Nov 19 2021 2:23:07 pm | state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
Fri, Nov 19 2021 2:23:07 pm | File "/usr/local/lib/python3.8/site-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards
Fri, Nov 19 2021 2:23:07 pm | state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
Fri, Nov 19 2021 2:23:07 pm | File "/usr/local/lib/python3.8/site-packages/django/db/migrations/executor.py", line 227, in apply_migration
Fri, Nov 19 2021 2:23:07 pm | state = migration.apply(state, schema_editor)
Fri, Nov 19 2021 2:23:07 pm | File "/usr/local/lib/python3.8/site-packages/django/db/migrations/migration.py", line 124, in apply
Fri, Nov 19 2021 2:23:07 pm | operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
Fri, Nov 19 2021 2:23:07 pm | File "/usr/local/lib/python3.8/site-packages/django/db/migrations/operations/fields.py", line 166, in database_forwards
Fri, Nov 19 2021 2:23:07 pm | schema_editor.remove_field(from_model, from_model._meta.get_field(self.name))
Fri, Nov 19 2021 2:23:07 pm | File "/usr/local/lib/python3.8/site-packages/django/db/backends/base/schema.py", line 510, in remove_field
Fri, Nov 19 2021 2:23:07 pm | return self.delete_model(field.remote_field.through)
Fri, Nov 19 2021 2:23:07 pm | File "/usr/local/lib/python3.8/site-packages/django/db/backends/base/schema.py", line 342, in delete_model
Fri, Nov 19 2021 2:23:07 pm | self.execute(self.sql_delete_table % {
Fri, Nov 19 2021 2:23:07 pm | File "/usr/local/lib/python3.8/site-packages/django/db/backends/base/schema.py", line 142, in execute
Fri, Nov 19 2021 2:23:07 pm | cursor.execute(sql, params)
Fri, Nov 19 2021 2:23:07 pm | File "/usr/local/lib/python3.8/site-packages/django/db/backends/utils.py", line 66, in execute
Fri, Nov 19 2021 2:23:07 pm | return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
Fri, Nov 19 2021 2:23:07 pm | File "/usr/local/lib/python3.8/site-packages/django/db/backends/utils.py", line 75, in _execute_with_wrappers
Fri, Nov 19 2021 2:23:07 pm | return executor(sql, params, many, context)
Fri, Nov 19 2021 2:23:07 pm | File "/usr/local/lib/python3.8/site-packages/django/db/backends/utils.py", line 84, in _execute
Fri, Nov 19 2021 2:23:07 pm | return self.cursor.execute(sql, params)
Fri, Nov 19 2021 2:23:07 pm | File "/usr/local/lib/python3.8/site-packages/django/db/utils.py", line 90, in __exit__
Fri, Nov 19 2021 2:23:07 pm | raise dj_exc_value.with_traceback(traceback) from exc_value
Fri, Nov 19 2021 2:23:07 pm | File "/usr/local/lib/python3.8/site-packages/django/db/backends/utils.py", line 84, in _execute
Fri, Nov 19 2021 2:23:07 pm | return self.cursor.execute(sql, params)
Fri, Nov 19 2021 2:23:07 pm | File "/usr/local/lib/python3.8/site-packages/django/db/backends/mysql/base.py", line 73, in execute
Fri, Nov 19 2021 2:23:07 pm | return self.cursor.execute(query, args)
Fri, Nov 19 2021 2:23:07 pm | File "/usr/local/lib/python3.8/site-packages/MySQLdb/cursors.py", line 206, in execute
Fri, Nov 19 2021 2:23:07 pm | res = self._query(query)
Fri, Nov 19 2021 2:23:07 pm | File "/usr/local/lib/python3.8/site-packages/MySQLdb/cursors.py", line 319, in _query
Fri, Nov 19 2021 2:23:07 pm | db.query(q)
Fri, Nov 19 2021 2:23:07 pm | File "/usr/local/lib/python3.8/site-packages/MySQLdb/connections.py", line 259, in query
Fri, Nov 19 2021 2:23:07 pm | _mysql.connection.query(self, query)
Fri, Nov 19 2021 2:23:07 pm | django.db.utils.OperationalError: (1051, "Unknown table 'jumpserver.assets_asset_protocols'")
Fri, Nov 19 2021 2:23:08 pm | 2021-11-19 14:23:08 Perform migrate failed, exit
Fri, Nov 19 2021 2:23:08 pm | Applying assets.0034_auto_20190705_1348...

Bug 重现步骤(有截图更好)

使用最新的helm 包安装 git clone https://github.com/jumpserver/helm
修改 value.yaml使用外部 redis和mysql
helm install jumpserver . -n jumpserver
后jumpserver-jms-init-db job一直失败,日志如上。

[Question] microk8s 部署后websokcet一直提示无法连接

请描述您的问题.
使用microk8s部署jumpser后使用ingress暴露服务，域名访问web端是正常的，但是登录后websocket无法连接，按照网上文章修改ingress 后还是无法解决
下面是我的ingress

[Question] Persistence Access Mode

Hi.

Is it possible to run using ReadWriteOnce instead of ReadWriteMany?

Trying to use it throws the following events:

Events:
  Type     Reason              Age                  From                     Message
  ----     ------              ----                 ----                     -------
  Warning  FailedScheduling    24m                  default-scheduler        0/6 nodes are available: 6 pod has unbound immediate PersistentVolumeClaims. preemption: 0/6 nodes are available: 6 Preemption is not helpful for scheduling.
  Warning  FailedScheduling    24m                  default-scheduler        0/6 nodes are available: 6 pod has unbound immediate PersistentVolumeClaims. preemption: 0/6 nodes are available: 6 Preemption is not helpful for scheduling.
  Normal   Scheduled           24m                  default-scheduler        Successfully assigned jumpserver/jumpserver-2-1672532068-jms-core-c9b85fd58-8jp7v to hive-srv-work-4
  Warning  FailedAttachVolume  24m                  attachdetach-controller  Multi-Attach error for volume "pvc-df0557c9-3f5b-46e7-b010-e77f02613728" Volume is already used by pod(s) jumpserver-2-1672532068-jms-celery-6ffc6d4464-rmhgr
  Warning  FailedAttachVolume  24m                  attachdetach-controller  Multi-Attach error for volume "pvc-e55aab2f-555e-466f-ac04-796d864bdd22" Volume is already used by pod(s) jumpserver-2-1672532068-jms-celery-6ffc6d4464-rmhgr
  Warning  FailedMount         6m49s (x2 over 11m)  kubelet                  Unable to attach or mount volumes: unmounted volumes=[jms-core-data jms-core-logs], unattached volumes=[jms-core-data jms-core-logs kube-api-access-vzc7l jms-core-config]: timed out waiting for the condition
  Warning  FailedMount         4m34s (x4 over 18m)  kubelet                  Unable to attach or mount volumes: unmounted volumes=[jms-core-data jms-core-logs], unattached volumes=[jms-core-config jms-core-data jms-core-logs kube-api-access-vzc7l]: timed out waiting for the condition
  Warning  FailedMount         2m18s (x2 over 22m)  kubelet                  Unable to attach or mount volumes: unmounted volumes=[jms-core-logs jms-core-data], unattached volumes=[jms-core-logs kube-api-access-vzc7l jms-core-config jms-core-data]: timed out waiting for the condition
  Warning  FailedMount         1s (x3 over 20m)     kubelet                  Unable to attach or mount volumes: unmounted volumes=[jms-core-data jms-core-logs], unattached volumes=[kube-api-access-vzc7l jms-core-config jms-core-data jms-core-logs]: timed out waiting for the condition

Thanks.

[Bug]

JumpServer 版本(v1.5.9以下不再支持)
helm部署， 2.24.2版本，部署完成后无法创建节点

浏览器版本

Bug 描述

Bug 重现步骤(有截图更好)
1.

[Bug] helm安装不能正常部署

JumpServer 版本(v1.5.9以下不再支持)
latest

浏览器版本
chrome latest

Bug 描述
helm安装指定了storage-class ，但是没有自动创建storage-class, 导致helm不能正常创建，望修复。

Question: How to modify the ansible.cfg file ? 🤔

Hi there.

I have deployed Jumpserver release 3.4.1 using default Helm Chart values. When trying to run some shortcut command, I get the following error on some Linux Asset: (screenshot)

STAGE-SSH-Instancia1 | UNREACHABLE! => {
    "changed": false,
    "msg": "Failed to create temporary directory. In some cases, you may have been able to authenticate and did not have permissions on the target directory. Consider changing the remote tmp path in ansible.cfg to a path rooted in \"/tmp\", for more error information use -vvv. Failed command was: ( umask 77 && mkdir -p \"` echo ~1.ent-mjvc35zcunzn4-staging-5em2ouy/.ansible/tmp `\"&& mkdir \"` echo ~1.ent-mjvc35zcunzn4-staging-5em2ouy/.ansible/tmp/ansible-tmp-1688159955.7952263-6855-273775216127374 `\" && echo ansible-tmp-1688159955.7952263-6855-273775216127374=\"` echo ~1.ent-mjvc35zcunzn4-staging-5em2ouy/.ansible/tmp/ansible-tmp-1688159955.7952263-6855-273775216127374 `\" ), exited with result 1",
    "unreachable": true
}

As the error states, I shoud "Consider changing the remote tmp path in ansible.cfg". Where can I update the "ansible.cfg" file ? I dont know where to edit the ansible.cfg file....

Thanks !

PS: By the way, I try adding the DEFAULT_LOCAL_TMP path value in the Platform section (image) but it did not work.

[Bug] 从2.8.5升级至2.8.20时失败

JumpServer 版本(v1.5.9以下不再支持)
当前版本 2.8.5
计划升级版本2.8.20

浏览器版本
Chrome Version 117.0.5938.92 (Official Build) (64-bit)

Bug 描述
helm 部署在k8s上
目前使用的values模板是2.8.5的
升级时改了tag为2.8.20
升级命令：helm upgrade jms-k8s jumpserver/jumpserver -f values.yaml -n jumpserver
提示错误：
Error: UPGRADE FAILED: cannot patch "jms-k8s-jumpserver-jms-core" with kind Deployment: Deployment.apps "jms-k8s-jumpserver-jms-core" is invalid: spec.template.spec.containers[0].livenessProbe.httpGet: Forbidden: may not specify more than 1 handler type

Bug 重现步骤(有截图更好)

修改values文件（版本2.8.5）中image tag为2.8.5
升级部署helm upgrade jms-k8s jumpserver/jumpserver -f values.yaml -n jumpserver
提示错误：Error: UPGRADE FAILED: cannot patch "jms-k8s-jumpserver-jms-core" with kind Deployment: Deployment.apps "jms-k8s-jumpserver-jms-core" is invalid: spec.template.spec.containers[0].livenessProbe.httpGet: Forbidden: may not specify more than 1 handler type
服务状态

[Question] docker image 没有更新

docker image 没有更新

docker pull ghcr.io/jumpserver/core:v3.2.2
Error response from daemon: manifest unknown

[Question] 为啥helm的版本不同步啊？隔壁都3.2.1了

请描述您的问题.
帮助文档的helm方式写的也是3.2.1，但是实际验证只有3.1.2版本可用。在线安装也3.2.1了。
旧的2.x版本也同样的问题，helm方式最新版本都没有。是helm方式可以放弃了的意思吗？

[Question] helm 升级时 jms-init-db 报错 'acls_connectmethodacl' already exists

helm upgrade 从3.4.1升级到3.4.3和3.6.1都失败。
job jms-init-db pods 返回：
django.db.utils.OperationalError: (1050, "Table 'acls_connectmethodacl' already exists")

[Bug] values.yaml 中 externalDatabase 与 externalRedis 的配置注释写反了

JumpServer 版本(v1.5.9以下不再支持)
v2.18.0

浏览器版本
无

Bug 描述

values.yaml 中 externalDatabase 与 externalRedis 的配置注释写反了

Bug 重现步骤(有截图更好)

helm-charts/charts/jumpserver/values.yaml

Lines 23 to 40 in e825e1c

 ## If the Redis database included in the chart is disabled, JumpServer will 

 ## use below parameters to connect to an external Redis server. 

 ## 

 externalDatabase: 

 engine: mysql 

 host: localhost 

 port: 3306 

 user: root 

 password: "" 

 database: jumpserver 

 ## If the MySQL database included in the chart is disabled, JumpServer will 

 ## use below parameters to connect to an external MySQL server. 

 ## 

 externalRedis: 

 host: localhost 

 port: 6379 

 password: ""

[Bug] core-ce:$.Chart.AppVersion: invalid reference format

[Bug] web一直启动失败，service-chen.yaml没有创建

JumpServer 版本(v1.5.9以下不再支持)
3.5.1

浏览器版本

Bug 描述
web一直启动失败，nginx配置里配置了chen的代理，因为service-chen.yaml没有创建

Bug 重现步骤(有截图更好)

	## If the Redis database included in the chart is disabled, JumpServer will
	## use below parameters to connect to an external Redis server.
	##
	externalDatabase:
	engine: mysql
	host: localhost
	port: 3306
	user: root
	password: ""
	database: jumpserver

	## If the MySQL database included in the chart is disabled, JumpServer will
	## use below parameters to connect to an external MySQL server.
	##
	externalRedis:
	host: localhost
	port: 6379
	password: ""

jumpserver / helm-charts Goto Github PK

helm-charts's People

Contributors

Stargazers

Watchers

Forkers

helm-charts's Issues

Recommend Projects

Recommend Topics

Recommend Org