話說 gitlab-ce 升級到 17.0.0 就壞掉了

[2024-05-19T16:56:57+08:00] ERROR: Exception handlers complete
Infra Phase failed. 13 resources updated in 18 seconds
[2024-05-19T16:56:57+08:00] FATAL: Stacktrace dumped to /opt/gitlab/embedded/cookbooks/cache/cinc-stacktrace.out
[2024-05-19T16:56:57+08:00] FATAL: ---------------------------------------------------------------------------------------
[2024-05-19T16:56:57+08:00] FATAL: PLEASE PROVIDE THE CONTENTS OF THE stacktrace.out FILE (above) IF YOU FILE A BUG REPORT
[2024-05-19T16:56:57+08:00] FATAL: ---------------------------------------------------------------------------------------
[2024-05-19T16:56:57+08:00] FATAL: RuntimeError: version_file[Create version file for Gitlab KAS] (gitlab-kas::enable line 67) had an error: RuntimeError: Execution of the command `/opt/gitlab/embedded/bin/gitlab-kas --version` failed with a non-zero exit code (2)
stdout: 
stderr: panic: failed to parse "2024-05-15T09:24:36+0000" into RFC3339 compliant time object, because: parsing time "2024-05-15T09:24:36+0000" as "2006-01-02T15:04:05Z07:00": cannot parse "+0000" as "Z07:00". Fix the build process.

goroutine 1 [running]:
gitlab.com/gitlab-org/cluster-integration/gitlab-agent/v17/cmd.init.0()
	/var/cache/omnibus/src/gitlab-kas/cmd/build_info.go:18 +0xf3


===
There was an error running gitlab-ctl reconfigure. Please check the output above for more
details.
===
warning: %posttrans(gitlab-ce-17.0.0-ce.0.el7.x86_64) scriptlet failed, exit status 1
Non-fatal POSTTRANS scriptlet failure in rpm package gitlab-ce-17.0.0-ce.0.el7.x86_64
  Verifying  : gitlab-ce-17.0.0-ce.0.el7.x86_64                                                                                                  1/2 
  Verifying  : gitlab-ce-16.11.2-ce.0.el7.x86_64                                                                                                 2/2 

Updated:
  gitlab-ce.x86_64 0:17.0.0-ce.0.el7                                                                                                                 

Complete!

連網頁也不能連

嗯...無法連線到此頁面

以上是 centos 7 的環境下失敗的

所以再測試了 centos 8 與 centos 9

是可以成功從 gitlab-ce-16.11.2 升級到 gitlab-ce-17.0.0

Restarting previously running GitLab services
ok: run: alertmanager: (pid 4358) 0s
ok: run: gitaly: (pid 4349) 0s
ok: run: gitlab-exporter: (pid 4346) 1s
ok: run: gitlab-kas: (pid 4369) 1s
ok: run: gitlab-workhorse: (pid 4331) 2s
ok: run: logrotate: (pid 4379) 0s
ok: run: nginx: (pid 4385) 1s
ok: run: node-exporter: (pid 4391) 0s
ok: run: postgres-exporter: (pid 4396) 1s
ok: run: postgresql: (pid 2671) 696s
ok: run: prometheus: (pid 4403) 0s
ok: run: puma: (pid 4409) 0s
ok: run: redis: (pid 2583) 713s
ok: run: redis-exporter: (pid 4416) 1s
ok: run: sidekiq: (pid 4425) 0s

     _______ __  __          __
    / ____(_) /_/ /   ____ _/ /_
   / / __/ / __/ /   / __ `/ __ \
  / /_/ / / /_/ /___/ /_/ / /_/ /
  \____/_/\__/_____/\__,_/_.___/
  

Upgrade complete! If your GitLab server is misbehaving try running
  sudo gitlab-ctl restart
before anything else.
If you need to roll back to the previous version you can use the database
backup made during the upgrade (scroll up for the filename).


  Verifying        : gitlab-ce-17.0.0-ce.0.el8.x86_64                                                                                            1/2 
  Verifying        : gitlab-ce-16.11.2-ce.0.el8.x86_64                                                                                           2/2 

Upgraded:
  gitlab-ce-17.0.0-ce.0.el8.x86_64                                                                                                                   

Complete!

 

Related posts 相關文章
gitlab-ce 升級到 17.0.0 就壞掉了
More...
最近要小心 GitHub 上的 POC 庫,可能是惡意程式
More...
下載 GitHub 上某個目錄
More...
升級 AlmaLinux 8.4 到 AlmaLinux 8.5
More...

作者

留言

撰寫回覆或留言

發佈留言必須填寫的電子郵件地址不會公開。