Skip to content

Prow "Kubernetes Master Driver Latest" test is failing #1489

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

Closed
pwschuurman opened this issue Nov 7, 2023 · 3 comments
Closed

Prow "Kubernetes Master Driver Latest" test is failing #1489

pwschuurman opened this issue Nov 7, 2023 · 3 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@pwschuurman
Copy link
Contributor

Test has been failing since before August 15, 2023 (latest we have Prow job history for). Other tests ("Kubernetes Master Driver Canary Latest Sidecars") are also failing with the same error.

Failures: https://testgrid.k8s.io/provider-gcp-compute-persistent-disk-csi-driver#Kubernetes%20Master%20Driver%20Latest

Example Failure Log: https://gist.github.com/pwschuurman/e07040e70c6fb5dc3f1ba75ed7edd3c9

Failure Snippet:

�[1mOutput from proc 1:�[0m
    Nov  7 15:57:38.735: INFO: Driver loaded from path [/home/prow/go/src/sigs.k8s.io/gcp-compute-persistent-disk-csi-driver/test/k8s-integration/config/test-config.yaml]: &{DriverInfo:{Name:csi-gcepd-sc-balanced--no-volumesnapshotclass InTreePluginName: TestTags:[] MaxFileSize:0 SupportedSizeRange:{Max:64Ti Min:5Gi} SupportedFsType:map[:{} ext2:{} ext3:{} ext4:{} xfs:{}] SupportedMountOption:map[debug:{} noatime:{}] RequiredMountOption:map[] Capabilities:map[block:true controllerExpansion:true exec:true fsGroup:true multipods:true nodeExpansion:true offlineExpansion:true onlineExpansion:true persistence:true pvcDataSource:true topology:true] RequiredAccessModes:[] TopologyKeys:[topology.gke.io/zone] NumAllowedTopologies:1 StressTestOptions:0xc0008bb7b0 VolumeSnapshotStressTestOptions:<nil> PerformanceTestOptions:<nil>} StorageClass:{FromName:false FromFile:/home/prow/go/src/sigs.k8s.io/gcp-compute-persistent-disk-csi-driver/test/k8s-integration/config/sc-balanced.yaml FromExistingClassName:} SnapshotClass:{FromName:false FromFile: FromExistingClassName:} InlineVolumes:[] ClientNodeName: Timeouts:map[DataSourceProvision:480s]}
  �[1m�[38;5;9mUnknown Decorator�[0m
  �[38;5;243mtest/e2e/storage/external/external.go:177�[0m
    [Container] node was passed an unknown decorator: '"External Storage"'

    �[1mLearn more at:�[0m �[38;5;14m�[4mhttp://onsi.github.io/ginkgo/#node-decorators-overview�[0m

  �[1m�[38;5;9mUnknown Decorator�[0m
  �[38;5;243mtest/e2e/storage/external/external.go:177�[0m
    [Container] node was passed an unknown decorator: '"[Driver:
    csi-gcepd-sc-balanced--no-volumesnapshotclass]"'

    �[1mLearn more at:�[0m �[38;5;14m�[4mhttp://onsi.github.io/ginkgo/#node-decorators-overview�[0m

Seems that k/k test is not able to parse the passed in decorator. https://github.com/kubernetes/kubernetes/tree/master/test/e2e/storage/external/external.go. Perhaps we should switch to using --label-filter for running test (kubernetes/kubernetes#121391).

@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 Feb 5, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active 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 rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 6, 2024
@pwschuurman
Copy link
Contributor Author

Fixed in kubernetes/kubernetes#121790

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

3 participants