search

kubernetes-retired / etcdadm

[EOL] etcdadm is a command-line tool for operating an etcd cluster
Apache License 2.0
765 stars 135 forks source link

etcd-manager: Bootstrap in Azure fails to mount data disk #381

Closed elias5000 closed 6 months ago

elias5000 commented 1 year ago

I tried to install a K8S cluster in Azure using the lastest kOps version (1.27.0). kOps uses etcd-manager to bootstrap etcd clusters.

When a VM has bootet up etcd-manager looks up the disk suitable for the control-plane node it is running on and tries to mount it. It then adds it to the vm and asks Azure API to update the VM accordingly. This operation fails with following error:

2023-07-18T08:59:59.394326417Z stdout F W0718 08:59:59.394109    7793 mounter.go:309] Error attaching volume "/subscriptions/<subcription-id>/resourceGroups/dev-rsg-tg-sandbox/providers/Microsoft.Compute/disks/etcd-1.etcd-events.kops-test.k8s.local": error updating VM: error updating VM Scale Set VM: compute.VirtualMachineScaleSetVMsClient#Update: Failure sending request: StatusCode=0 -- Original Error: autorest/azure: Service returned an error. Status=<nil> Code="PropertyChangeNotAllowed" Message="Changing property 'dataDisk.name' is not allowed." Target="dataDisk.name"

The codes breaks at this position where Azure apparently dislikes the name set for the datadisk: https://github.com/kubernetes-sigs/etcdadm/blob/master/etcd-manager/pkg/volumes/azure/volumes.go#L222-L236

Subsequently etcd-manager is not able to assemble the cluster.

hakman commented 1 year ago

@elias5000 Could you try with kOps 1.28.0? I've been trying to make Azure integration work better for some time now.

k8s-triage-robot commented 8 months ago

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

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

You can:

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

/lifecycle stale

k8s-triage-robot commented 7 months ago

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:

You can:

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

/lifecycle rotten

k8s-triage-robot commented 6 months ago

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

This bot triages issues according to the following rules:

You can:

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

/close not-planned

k8s-ci-robot commented 6 months ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes-sigs/etcdadm/issues/381#issuecomment-2026588257): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages 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: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.