diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-07-16 12:09:22 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-07-16 12:09:22 +0000 |
| commit | 9d67bc14cb59a27c9877474e77d155173a1dedff (patch) | |
| tree | fae9da04bb838c0bf93df6ba7669c15413e99f8e /doc/administration/geo/replication/geo_validation_tests.md | |
| parent | 9c7b3812a22465b77ee24657ad1b446b81ffbc74 (diff) | |
| download | gitlab-ce-9d67bc14cb59a27c9877474e77d155173a1dedff.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/administration/geo/replication/geo_validation_tests.md')
| -rw-r--r-- | doc/administration/geo/replication/geo_validation_tests.md | 19 |
1 files changed, 15 insertions, 4 deletions
diff --git a/doc/administration/geo/replication/geo_validation_tests.md b/doc/administration/geo/replication/geo_validation_tests.md index 22ba574dae5..0255e5c9883 100644 --- a/doc/administration/geo/replication/geo_validation_tests.md +++ b/doc/administration/geo/replication/geo_validation_tests.md @@ -16,11 +16,22 @@ This section contains a journal of recent validation tests and links to the rele The following are GitLab upgrade validation tests we performed. +### July 2020 + +[Upgrade Geo multi-node installation](https://gitlab.com/gitlab-org/gitlab/-/issues/225359): + +- Description: Tested upgrading from GitLab 12.10.12 to 13.0.10 package in a multi-node + configuration. As part of the issue to [Fix zero-downtime upgrade process/instructions for multi-node Geo deployments](https://gitlab.com/gitlab-org/gitlab/-/issues/22568), we monitored for downtime using the looping pipeline, HAProxy stats dashboards, and a script to log readiness status on both nodes. +- Outcome: Partial success because we observed downtime during the upgrade of the primary and secondary sites. +- Follow up issues/actions: + - [Investigate why `reconfigure` and `hup` cause downtime on multi-node Geo deployments](https://gitlab.com/gitlab-org/gitlab/-/issues/228898) + - [Geo multi-node deployment upgrade: investigate order when upgrading non-deploy nodes](https://gitlab.com/gitlab-org/gitlab/-/issues/228954) + ### June 2020 -[Upgrade Geo multi-server installation](https://gitlab.com/gitlab-org/gitlab/-/issues/223284): +[Upgrade Geo multi-node installation](https://gitlab.com/gitlab-org/gitlab/-/issues/223284): -- Description: Tested upgrading from GitLab 12.9.10 to 12.10.12 package in a multi-server +- Description: Tested upgrading from GitLab 12.9.10 to 12.10.12 package in a multi-node configuration. Monitored for downtime using the looping pipeline and HAProxy stats dashboards. - Outcome: Partial success because we observed downtime during the upgrade of the primary and secondary sites. - Follow up issues/actions: @@ -28,9 +39,9 @@ The following are GitLab upgrade validation tests we performed. - [Geo:check Rake task: Exclude AuthorizedKeysCommand check if node not running Puma/Unicorn](https://gitlab.com/gitlab-org/gitlab/-/issues/225454) - [Update instructions in the next upgrade issue to include monitoring HAProxy dashboards](https://gitlab.com/gitlab-org/gitlab/-/issues/225359) -[Upgrade Geo multi-server installation](https://gitlab.com/gitlab-org/gitlab/-/issues/208104): +[Upgrade Geo multi-node installation](https://gitlab.com/gitlab-org/gitlab/-/issues/208104): -- Description: Tested upgrading from GitLab 12.8.1 to 12.9.10 package in a multi-server +- Description: Tested upgrading from GitLab 12.8.1 to 12.9.10 package in a multi-node configuration. - Outcome: Partial success because we did not run the looping pipeline during the demo to validate zero-downtime. |