Files

T

Ian Littman f4f249a5eb Only use one nginx worker, add a slight wait post-nginx-reload, to properly upgrade-test schema changes that aren't backward-compatible on the "get enroll secret" code path (#26008 )

For #26003. Will add more context to that ticket.

This is a robustness fix to the upgrade test, which pulls tags/branches
from Docker, so this does _not_ need to be cherry-picked.

To confirm this fix, run the upgrade test from <4.63.0 to >= 4.63.0 and
see it pass rather than fail.

# Checklist for submitter
- [x] Added/updated automated tests
- [x] A detailed QA plan exists on the associated ticket (if it isn't
there, work with the product group's QA engineer to add it)
- [x] Manual QA for all new/changed functionality

2025-02-03 19:55:26 -06:00

nginx

…

docker-compose.yaml

MySQL 8.0 Migration (#20225 )

2024-07-22 16:27:36 -04:00

fleet_test.go

Only use one nginx worker, add a slight wait post-nginx-reload, to properly upgrade-test schema changes that aren't backward-compatible on the "get enroll secret" code path (#26008 )

2025-02-03 19:55:26 -06:00

fleet.crt

…

fleet.key

…

generate_cert.sh

…

osquery.flags

…

README.md

…

upgrade_test.go

…

README.md

Upgrade Tests

The tests located in test/upgrade are intended to test fleet upgrades with online migrations as proposed in #6376. To run the tests, you need to specify the from and to versions. For example

$ FLEET_VERSION_A=v4.16.0 FLEET_VERSION_B=v4.18.0 go test ./test/upgrade

Ensure that Docker is installed with Compose V2. To check if you have the correct version, run the following command

$ docker compose version
Docker Compose version v2.6.0