This reverts merge request !60

Adapting the patch from https://sourceforge.net/p/graphicsmagick/code/ci/50395430a37188d0d197e71bd85ed6dd0f649ee3/

Patch for CVE-2019-3881

DJ Mountney authored 4 years ago and GitLab Release Tools Bot committed 4 years ago

Resolve "gitlab-ctl patroni members results in error with prettytable"

Closes #5701

See merge request gitlab-org/omnibus-gitlab!4628

(cherry picked from commit ca09a5da)

1032d527 Force installation of PrettyTable 0.7
dc382dcf Use the correct version number

Ian Baum authored 4 years ago and DJ Mountney committed 4 years ago

* Updating multiple components to the latest available version

Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>

Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>

Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>

* Update node_exporter to 1.0.1.
* Update Prometheus to 2.20.1.
* Update pgbouncer_exporter to 0.4.0.
* Update redis_exporter to 1.6.1.
* Redis exporter doesn't use inline vendor data anymore.

Signed-off-by: Ben Kochie <bjk@gitlab.com>

Balasankar C authored 4 years ago and DJ Mountney committed 4 years ago

Signed-off-by: Balasankar "Balu" C <balasankarc@autistici.org>

This reverts commit b3c31ec9, reversing
changes made to 8d004a2a.

This reverts merge request !4459

This will help unblock the upgrade to Ruby 2.7 since gRPC and
google-protobuf need a more recent compiler.

As explained in https://stackoverflow.com/a/15602073/1992201:

The whole point of devtoolset is that it allows you to use a newer GCC
and newer libstdc++ but without creating any run-time dependencies on
the newer libstdc++ library. The compiled executables only need the
system version of libstdc++.so that is always present on RHEL/CentOS,
even systems without devtoolset installed. (What devtoolset does is
package all the new libstdc++ features in a static library, called
libstdc++_nonshared.a so that all the pieces not present in the system
libstdc++.so get statically linked in, and everything else will come
from the system libstdc++.so).

Gitaly is moving its default and minimum required version of Git to
v2.28.0. So let's move our default version to match this new
requirement.

This reverts commit 9f1d2e9d, reversing
changes made to 6c09a717.

Hossein Pursultani authored 4 years ago and DJ Mountney committed 4 years ago

PostgreSQL 12 is opt-in only and limited to single database node
installation.

This updates the Grafana dashboards to v1.8.0. This new version
includes an enhancement for the Omnibus Gitaly dashboard that
enables Gitaly nodes in a Praefect cluster to be visible via
a selection in a dropdown box.

Related to https://gitlab.com/gitlab-org/gitaly/-/issues/2838

[┐∵]┘GitLab Dependency Bot authored 4 years ago and Ian Baum committed 4 years ago

* Switch to ruby 2.6
* Update all usage of the ruby image to use RUBY_IMAGE variable

Latest upgrade has added a Makefile

Updates ohai and mixlib-log to match what we use in our spec testing,
and what is default for the included chef version

Ian Baum authored 4 years ago and DJ Mountney committed 4 years ago

* Curently on 14, which was set to end of life at on April 30, 2020.
* Adds chef-bin gem
* Automatically accept the chef license EULA
* Update chef libraries in Gemfile to newer versions
* Update trigger jobs to use ruby 2.6 image

- Updates PCRE to version 8.44

Closes https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/5457



Signed-off-by: Robert Marshall <rmarshall@gitlab.com>

Display read-only mode status in shard status panel

https://gitlab.com/gitlab-org/grafana-dashboards/-/merge_requests/49

https://gitlab.com/gitlab-org/gitaly/-/issues/2789



Signed-off-by: Ben Kochie <bjk@gitlab.com>

Ben Kochie authored 4 years ago and Balasankar C committed 4 years ago

Update to latest Grafana.

https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/10347



Signed-off-by: Ben Kochie <bjk@gitlab.com>

Calls to the `copy_file_range()` system call on recent RedHat kernels
now fail with `EOPNOTSUP` instead of `ENOSYS`, which breaks any use of
`IO.copy_stream` (e.g. used by CarrierWave) if NFS is used.

Ruby attempts to detect whether the kernel supports this system call,
but the detection mechanism only checks whether this system call is
defined, not whether it is actually supported. We manually patch this to
disable the `copy_file_range()`.

Relates to:
1. https://bugs.ruby-lang.org/issues/16965
2. https://gitlab.com/gitlab-org/gitlab/-/issues/218999
3. https://bugzilla.redhat.com/show_bug.cgi?id=1783554