ubicloud/spec/prog/test
Enes Cakir 038ed5eb40 Verify VM host resources are reclaimed correctly
Recently, we had a production bug where the destroy label for a VM ran
twice, causing the VM host resources to be reclaimed twice. This
resulted in negative resource values and failed constraints. Adding a
check in the E2E tests will help verify this case. While it may not
catch every edge case, it will at least cover the basic scenario.
2025-10-04 16:10:19 +03:00
..
connected_subnets_spec.rb Change all create_with_id to create 2025-08-06 01:55:51 +09:00
firewall_rules_spec.rb Change all create_with_id to create 2025-08-06 01:55:51 +09:00
github_runner_spec.rb Fix a test on the main 2025-03-24 21:23:57 +03:00
ha_postgres_resource_spec.rb Wait for postgres resources to be fully destroyed in E2E tests 2025-10-04 15:56:49 +03:00
hetzner_server_spec.rb Verify VM host resources are reclaimed correctly 2025-10-04 16:10:19 +03:00
kubernetes_spec.rb Add normal restart e2e test to CSI 2025-09-24 11:59:14 +02:00
postgres_resource_spec.rb Wait for postgres resources to be fully destroyed in E2E tests 2025-10-04 15:56:49 +03:00
vm_group_spec.rb Change all create_with_id to create 2025-08-06 01:55:51 +09:00
vm_host_slices_spec.rb Update E2E tests for Burstables 2025-02-19 09:20:28 -08:00
vm_spec.rb Change all create_with_id to create 2025-08-06 01:55:51 +09:00