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

Azure storage tests are not working #82272

Closed
jsafrane opened this issue Sep 3, 2019 · 4 comments · Fixed by #82324
Closed

Azure storage tests are not working #82272

jsafrane opened this issue Sep 3, 2019 · 4 comments · Fixed by #82324
Labels
kind/bug Categorizes issue or PR as related to a bug. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider.

Comments

@jsafrane
Copy link
Member

jsafrane commented Sep 3, 2019

I am trying to run Azure e2e tests:

go run hack/e2e.go  -- --test  --test_args="--ginkgo.focus=azure.*Inline.*file -kubeconfig=$KUBECONFIG --provider=azure -cloud-config-file $PWD/azure.cfg  " --check-version-skew=false

The test creates a volume in the cloud + runs a pod with the volume as in-line. The pod never starts:

Warning  FailedAttachVolume  13s (x6 over 31s)  attachdetach-controller  AttachVolume.Attach failed for volume "vol1" : Attach volume "jsafrane-e2e-41eb8696-5c88-4906-a8c3-debf71f7b856.vhd" to instance "/subscriptions/a6665e84-ec61-4111-a6d3-db3903e202dc/resourceGroups/jsafrane-dev-6t8r2-rg/providers/Microsoft.Compute/virtualMachines/jsafrane-dev-6t8r2-worker-centralus2-5m9r8" failed with compute.VirtualMachinesClient#CreateOrUpdate: Failure sending request: StatusCode=0 -- Original Error: autorest/azure: Service returned an error. Status=<nil> Code="OperationNotAllowed" Message="Addition of a blob based disk to VM with managed disks is not supported." Target="dataDisk"

The test creates a "blob" disk, while the Azure machine expects "managed" disk.

Does anyone run storage e2e tests on Azure regularly? Was it ever working? Managed disks are provisioned by default. Should the test suite create "managed" disks by default too?

@kubernetes/provider-azure @andyzhangx

Environment:

  • Kubernetes version (use kubectl version): v1.17.0-alpha.0.1089+dbc6fcfc75e956-dirty
@jsafrane jsafrane added the kind/bug Categorizes issue or PR as related to a bug. label Sep 3, 2019
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Sep 3, 2019
@jsafrane
Copy link
Member Author

jsafrane commented Sep 3, 2019

/sig azure

@jsafrane
Copy link
Member Author

jsafrane commented Sep 3, 2019

/sig cloud-provider

@k8s-ci-robot k8s-ci-robot added sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Sep 3, 2019
@andyzhangx
Copy link
Member

managed disk should be the default, the azure disk storage class in the test case may have kind=Shared

@jsafrane
Copy link
Member Author

jsafrane commented Sep 3, 2019

The volume is created outside of kubernetes dynamic provisioning to test pre-provisioned and inline volumes:

func (p *Provider) CreatePD(zone string) (string, error) {

I wonder if anyone actually runs the tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants