gitlab第一次登录修改密码失败

Choerodon Installation management
#1
  • Choerodon平台版本:0.25.0

image
image1920×937 42.2 KB

部署持续交付的时候要部署gitlab-service，需要获取gitlab的token，但是按照文档说的gitlab页面可以打开就是部署成功了，第一次进入直接修改密码，修改不了，如图所示。该怎么办？

#2

没人碰到过这么问题吗

#3

你输入的密码不符合要求，请按照提示条件输入密码。

#6

这密码要求是啥啊 提示信息说emal namespace name不能为空。。 我去注册了gitlab官网只要求了8位

#7

你好，我设置密码1qaz!QAZ或者1234qwer或者12345678都还是返回Change your password页面，救救救。

#8

1647232078(1)
1647232078(1)1654×472 65.4 KB

1647232078
16472320781920×937 77.7 KB

1647232125(1)
1647232125(1)1834×902 76.8 KB

core的日志看不出来什么， database的pod日志有这种提示不知道是否有影响？我应该从哪方面入手解决这个问题呢？一直卡在change password页面

#9

没人遇到过吗大佬们？

#10

你是分步安装的猪齿鱼？请贴一下你的 gitlab.yaml 文件。

#11 
core:
  env:
    OAUTH_ENABLED: false
    OAUTH_AUTO_SIGN_IN_WITH_PROVIDER: "oauth2_generic"
    OAUTH_ALLOW_SSO: "'oauth2_generic'"
    OAUTH_BLOCK_AUTO_CREATED_USERS: false
    OAUTH_GENERIC_API_KEY: "gitlabhq"
    OAUTH_GENERIC_APP_SECRET: "gitlabhq"
    # choerodon api 访问地址
    OAUTH_GENERIC_SITE: "http://api.example.choerodon.io"
    OAUTH_GENERIC_USER_INFO_URL: "/oauth/api/user"
    OAUTH_GENERIC_AUTHORIZE_URL: "/oauth/oauth/authorize"
    OAUTH_GENERIC_TOKEN_URL: "/oauth/oauth/token"
    OAUTH_GENERIC_ROOT_PATH: "'userAuthentication','principal'"
    OAUTH_GENERIC_ID_PATH: "'userAuthentication','principal','userId'"
    OAUTH_GENERIC_USER_NICKNAME: "username"
    OAUTH_GENERIC_USER_NAME: "usernmae"
    RACK_ATTACK_WHITELIST: 0.0.0.0/0
redis:
  internal:
    password: password
persistence:
  enabled: true
  persistentVolumeClaim:
    core:
      storageClass: nfs-provisioner
    redis:
      storageClass: nfs-provisioner
    database:
      storageClass: nfs-provisioner
expose:
  ingress:
    host: "gitlab.example.choerodon.io"
database:
  internal:
    password: "password"

就是官方文档上的yaml文件。
我现在已经全清了。。搞了个域名弄一键部署，又发现了一个问题。。我新开个帖子吧

#12 
2022-03-15T12:21:24.499990Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2022-03-15T12:21:25.521717Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2022-03-15T12:21:25.523398Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49472
2022-03-15T12:21:25.544492Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 2588005
2022-03-15T12:21:25.547391Z 0 [Note] InnoDB: Database was not shutdown normally!
2022-03-15T12:21:25.547399Z 0 [Note] InnoDB: Starting crash recovery.
2022-03-15T12:21:25.547466Z 0 [Warning] InnoDB: Retry attempts for reading partial data failed.
2022-03-15T12:21:25.547478Z 0 [ERROR] InnoDB: Tried to read 16384 bytes at offset 1064960, but was only able to read 0
2022-03-15T12:21:25.547487Z 0 [ERROR] InnoDB: Operating system error number 5 in a file operation.
2022-03-15T12:21:25.547500Z 0 [ERROR] InnoDB: Error number 5 means 'Input/output error'
2022-03-15T12:21:25.547503Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2022-03-15T12:21:25.547507Z 0 [ERROR] InnoDB: File (unknown): 'read' returned OS error 105. Cannot continue operation
2022-03-15T12:21:25.547510Z 0 [ERROR] InnoDB: Cannot continue operation.

image
image1920×937 71.1 KB

是内存不够吗？ 4个 4C16G的节点，硬盘也够啊

image
image1314×254 10.8 KB

#13

一键安装把