[DRE-maint] Bug#977636: gitlab: Package upgrade hangs indefinitely and consumes all CPU/memory
Maximilian Stein
m at steiny.biz
Thu Dec 17 21:49:55 GMT 2020
Package: gitlab
Version: 13.4.7-2~fto10+1
Severity: important
Dear Maintainer,
During an upgrade to version 13.4.7-1~fto10+1 or 13.4.7-2~fto10+1
there is a rake process in the postinst script that consumes 100 % cpu
and takes up a lot of memory but never finishes, even not after hours.
I finally killed the process with a SIGKILL, and gitlab seems to work
afterwards.
This is the last output I get during the installation:
-------------------- snip ------------------------------
yarn install v1.22.4
[1/4] Resolving packages...
success Already up-to-date.
$ node ./scripts/frontend/postinstall.js
success Dependency postinstall check passed.
Done in 1.90s.
WARNING on line 297, column 11 of /usr/share/gitlab/app/assets/stylesheets/framework/common.scss:
Compound selectors may no longer be extended.
Consider `@extend .card, .card-body` instead.
See http://bit.ly/ExtendCompound for details.
WARNING on line 208, column 13 of /usr/share/gitlab/app/assets/stylesheets/framework/filters.scss:
Compound selectors may no longer be extended.
Consider `@extend .form-control, :hover` instead.
See http://bit.ly/ExtendCompound for details.
WARNING on line 31, column 13 of /usr/share/gitlab/app/assets/stylesheets/pages/help.scss:
Compound selectors may no longer be extended.
Consider `@extend .badge, .badge-pill` instead.
See http://bit.ly/ExtendCompound for details.
WARNING on line 665, column 13 of /usr/share/gitlab/app/assets/stylesheets/pages/issuable.scss:
Compound selectors may no longer be extended.
Consider `@extend a, :hover` instead.
See http://bit.ly/ExtendCompound for details.
WARNING on line 580, column 15 of /usr/share/gitlab/app/assets/stylesheets/pages/pipelines.scss:
Compound selectors may no longer be extended.
Consider `@extend .build-content, :hover` instead.
See http://bit.ly/ExtendCompound for details.
-------------------- snip ------------------------------
Is there a known workaround for that issue?
Apparently, at least for me, a clean upgrade of gitlab is not possible
right now.
Best,
Maximilian
More information about the Pkg-ruby-extras-maintainers
mailing list