2.3 KiB
Redis component upgrade test plan
Test plan
-
Performed a successful GitLab Enterprise Edition (EE) build on all supported platforms (include
build-package-on-all-os
job). -
Ran
qa-subset-test
as well as manualqa-remaining-test-manual
CI/CD test job for both GitLab Enterprise Edition and GitLab Community Edition. -
Redis indicator test cases were not failing.
-
Performed fresh install and verified operation:
- Installed on single node
-
Checked installed version:
/opt/gitlab/embedded/bin/redis-server --version
-
Sign-in
-
Imported a project (confirms Sidekiq works)
-
Checked
gitlab-kas
log for Redis errors -
Checked
redis-exporter
logs for errors -
Confirmed
gitlab-redis-cli
command connects to Redis
-
- Installed on HA Sentinels (see https://docs.gitlab.com/ee/administration/redis/replication_and_failover.html)
- Signed-in
- Imported a project (confirms Sidekiq works)
- Checked
gitlab-kas
log for Redis errors - Performed failover
- Installed on single node
-
Updates
-
Updated on single node:
-
Verified that you get the message:
Running version of Redis different than installed version. Restart redis"
-
Sign-in
-
Imported a project (confirms Sidekiq works)
-
Checked
gitlab-kas log
for Redis errors -
Checked
redis-exporter logs
for errors -
Confirmed
gitlab-redis-cli
command connects to Redis
-
-
Updated HA Sentinel/Redis nodes (see https://docs.gitlab.com/ee/update/zero_downtime.html#redis-ha-using-sentinel)
-
Verified that you get the message:
Running version of Redis different than installed version. Restart redis"
-
Signed-in
-
Imported a project (confirms Sidekiq works)
-
Checked
gitlab-kas
log for Redis errors -
Checked
redis-exporter
logs for errors -
Confirmed
gitlab-redis-cli
command connects to Redis on a Redis node -
Performed failover
-
-