The disruptive test is flaky

[caesarxuchao]

See https://prow.k8s.io/job-history/kubernetes-jenkins/pr-logs/directory/pull-kube-storage-version-migrator-disruptive

[sanchezl]

In the failure cases, the StorageStates for the resource {migrationtest.k8s.io tests} are missing and the other are corrupted? ( ss.Status.PersistedStorageVersionHashes == 'Unknown'):

STEP: Wait for the storage state of the CRD to change
Dec 17 19:26:22.561: INFO: v1Hash is 6CkQIRTwz0g=
Dec 17 19:26:22.561: INFO: v2Hash is nBsJ5Ef70dU=
STEP: Wait for all storage states to converge
Dec 17 19:27:22.579: INFO: resource {cloud.google.com backendconfigs} has persisted hashes [Unknown], and current hash aO44pP311pE=
Dec 17 19:27:52.592: INFO: resource {cloud.google.com backendconfigs} has persisted hashes [Unknown], and current hash aO44pP311pE=
Dec 17 19:28:22.590: INFO: resource {cloud.google.com backendconfigs} has persisted hashes [Unknown], and current hash aO44pP311pE=
Dec 17 19:28:52.590: INFO: resource {cloud.google.com backendconfigs} has persisted hashes [Unknown], and current hash aO44pP311pE=
Dec 17 19:29:22.593: INFO: resource {apps daemonsets} has persisted hashes [Unknown], and current hash dd7pWHUlMKQ=
Dec 17 19:29:52.594: INFO: resource {events.k8s.io events} has persisted hashes [Unknown], and current hash r2yiGXH7wu8=
Dec 17 19:30:22.591: INFO: resource {events.k8s.io events} has persisted hashes [Unknown], and current hash r2yiGXH7wu8=
Dec 17 19:30:52.590: INFO: resource {events.k8s.io events} has persisted hashes [Unknown], and current hash r2yiGXH7wu8=
Dec 17 19:31:22.589: INFO: resource {events.k8s.io events} has persisted hashes [Unknown], and current hash r2yiGXH7wu8=
Dec 17 19:31:52.589: INFO: resource {events.k8s.io events} has persisted hashes [Unknown], and current hash r2yiGXH7wu8=
Dec 17 19:32:22.591: INFO: resource {events.k8s.io events} has persisted hashes [Unknown], and current hash r2yiGXH7wu8=
Dec 17 19:32:52.590: INFO: resource {events.k8s.io events} has persisted hashes [Unknown], and current hash r2yiGXH7wu8=
Dec 17 19:33:22.591: INFO: resource {events.k8s.io events} has persisted hashes [Unknown], and current hash r2yiGXH7wu8=
Dec 17 19:33:52.600: INFO: resource {events.k8s.io events} has persisted hashes [Unknown], and current hash r2yiGXH7wu8=
Dec 17 19:34:22.590: INFO: resource {events.k8s.io events} has persisted hashes [Unknown], and current hash r2yiGXH7wu8=
Dec 17 19:34:52.594: INFO: resource {events.k8s.io events} has persisted hashes [Unknown], and current hash r2yiGXH7wu8=
Dec 17 19:35:22.589: INFO: resource {events.k8s.io events} has persisted hashes [Unknown], and current hash r2yiGXH7wu8=
Dec 17 19:35:52.591: INFO: resource {events.k8s.io events} has persisted hashes [Unknown], and current hash r2yiGXH7wu8=
Dec 17 19:36:22.591: INFO: resource {events.k8s.io events} has persisted hashes [Unknown], and current hash r2yiGXH7wu8=
Dec 17 19:36:52.590: INFO: resource {events.k8s.io events} has persisted hashes [Unknown], and current hash r2yiGXH7wu8=
Dec 17 19:37:22.590: INFO: resource {events.k8s.io events} has persisted hashes [Unknown], and current hash r2yiGXH7wu8=
Dec 17 19:37:22.598: INFO: resource {events.k8s.io events} has persisted hashes [Unknown], and current hash r2yiGXH7wu8=
Dec 17 19:37:22.598: INFO: timed out waiting for the condition

Maybe the corruption scenario outlined in MigrationTrigger is occurring?

[sanchezl]

Looking at my previously posted log snippet:
{cloud.google.com backendconfigs} StorageState takes at least 2m to 2m30s to migrate
{app daemonsets} takes 30s to 1m.
We finally time out after {events.k8s.io events} has spent 8 minutes waiting to migrate.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[sanchezl]

Resolved by #58

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.