Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix pull-azuredisk-csi-driver-external-e2e-single-az test failure #2534

Open
andyzhangx opened this issue Sep 20, 2024 · 1 comment
Open
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@andyzhangx
Copy link
Member

Is your feature request related to a problem?/Why is this needed

Describe the solution you'd like in detail

https://storage.googleapis.com/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_azuredisk-csi-driver/2526/pull-azuredisk-csi-driver-external-e2e-single-az/1836952385784647680/build-log.txt

�[91m�[1mSummarizing 2 Failures:�[0m

�[91m�[1m[Fail] �[0m�[90mExternal Storage [Driver: test.csi.azure.com] �[0m�[0m[Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand �[0m�[91m�[1m[It] Verify if offline PVC expansion works �[0m
�[37mtest/e2e/storage/testsuites/volume_expand.go:222�[0m

�[91m�[1m[Fail] �[0m�[90mExternal Storage [Driver: test.csi.azure.com] �[0m�[0m[Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand �[0m�[91m�[1m[It] Verify if offline PVC expansion works �[0m
�[37mtest/e2e/storage/testsuites/volume_expand.go:222�[0m

�[1m�[91mRan 95 of 7227 Specs in 980.898 seconds�[0m
�[1m�[91mFAIL!�[0m -- �[32m�[1m93 Passed�[0m | �[91m�[1m2 Failed�[0m | �[33m�[1m0 Pending�[0m | �[36m�[1m7132 Skipped�[0m
�[91m�[1m• Failure [339.127 seconds]�[0m
External Storage [Driver: test.csi.azure.com]
�[90mtest/e2e/storage/external/external.go:174�[0m
  [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand
  �[90mtest/e2e/storage/framework/testsuite.go:50�[0m
    �[91m�[1mVerify if offline PVC expansion works [It]�[0m
    �[90mtest/e2e/storage/testsuites/volume_expand.go:176�[0m

    �[91mSep 20 02:57:47.745: While waiting for pvc to have fs resizing condition
    Unexpected error:
        <*errors.errorString | 0xc0025ff530>: {
            s: "error waiting for pvc \"test.csi.azure.coml5vg9\" to have filesystem resize status: timed out waiting for the condition",
        }
        error waiting for pvc "test.csi.azure.coml5vg9" to have filesystem resize status: timed out waiting for the condition
    occurred�[0m

    test/e2e/storage/testsuites/volume_expand.go:222
�[90m------------------------------�[0m
{"msg":"FAILED External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand Verify if offline PVC expansion works","total":-1,"completed":1,"skipped":55,"failed":1,"failures":["External Storage [Driver: test.csi.azure.com] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand Verify if offline PVC expansion works"]}

Describe alternatives you've considered

Additional context

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants