ubicloud/spec/prog/vnet
Enes Cakir 2e33ad0d30 Do not trigger subnet destroy deadline if the VM is already being destroyed
If the VM is stuck in the destroying state, we create pages for both the
private subnet and the VM. Since the VM is already being destroyed,
there’s no need to raise the subnet destroy deadline. I will help with
the page storms when the host is down.

The destroying state also includes the prevent_destroy state, so a
single check is sufficient.
2025-02-03 13:59:22 +03:00
..
cert_nexus_spec.rb Make access_tag only for project <-> accounts join table 2025-01-17 08:32:46 -08:00
cert_server_spec.rb Make access_tag only for project <-> accounts join table 2025-01-17 08:32:46 -08:00
load_balancer_nexus_spec.rb Add destroying label to prevent hop to destroy again 2025-02-03 12:02:02 +03:00
nic_nexus_spec.rb Mark project_id columns newly added to tables as NOT NULL 2025-01-17 12:47:51 -08:00
rekey_nic_tunnel_spec.rb Mark project_id columns newly added to tables as NOT NULL 2025-01-17 12:47:51 -08:00
subnet_nexus_spec.rb Do not trigger subnet destroy deadline if the VM is already being destroyed 2025-02-03 13:59:22 +03:00
update_firewall_rules_spec.rb Add private_ipv4 and private_ipv6 utility functions 2025-01-30 12:24:20 +01:00
update_load_balancer_node_spec.rb Make access_tag only for project <-> accounts join table 2025-01-17 08:32:46 -08:00