mirror of
https://github.com/kubernetes/kubernetes.git
synced 2026-05-24 02:46:18 -04:00
72b6f1b590
Subtest 5-2-3 starts the controller with both the claim and the volume already present and with the volume annotated as controller-bound. That setup depends on watch/list ordering during controller startup: if the initial objects are observed in a different order, the test can time out even though the controller later converges to the expected state. Model the scenario more explicitly. Start with the unbound volume only, then inject the claim through AddClaimEvent after the controller is running. Also drop the pre-set controller-bound annotation from the initial volume since the binding is what the test wants the controller to establish. Tested: go test -race ./pkg/controller/volume/persistentvolume -run TestControllerSync -count=50 |
||
|---|---|---|
| .. | ||
| attachdetach | ||
| common | ||
| ephemeral | ||
| events | ||
| expand | ||
| persistentvolume | ||
| protectionutil | ||
| pvcprotection | ||
| pvprotection | ||
| selinuxwarning | ||
| vacprotection | ||
| OWNERS | ||