search

kubermatic / machine-controller

Apache License 2.0
308 stars 131 forks source link

Fix VCD tests #1619

Open xrstf opened 1 year ago

xrstf commented 1 year ago

VCD e2e tests are currently failing with

Error: 400: [ a0acf93e-1c9e-4543-87ba-2e9a4585ebfa ] The entity Ref: com.vmware.vcloud.entity.vapp:6602ebbd-4b07-4aad-9909-022fad2e8efe is busy completing an operation VDC_RECOMPOSE_VAPP."} 2023-04-19T18:29:11.592Z error machine-controller machine/controller.go:402 Reconciling failed {"machine": "kube-system/ubuntu-1-26-1-vcd-1648753846731673600-5889b9cd

See for example #1606

kubermatic-bot commented 1 year ago

Issues go stale after 90d of inactivity. After a furter 30 days, they will turn rotten. Mark the issue as fresh with /remove-lifecycle stale.

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

/lifecycle stale

ahmedwaleedmalik commented 1 year ago

/remove-lifecycle stale

kubermatic-bot commented 1 year ago

Issues go stale after 90d of inactivity. After a furter 30 days, they will turn rotten. Mark the issue as fresh with /remove-lifecycle stale.

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

/lifecycle stale

ahmedwaleedmalik commented 1 year ago

/remove-lifecycle stale

kubermatic-bot commented 9 months ago

Issues go stale after 90d of inactivity. After a furter 30 days, they will turn rotten. Mark the issue as fresh with /remove-lifecycle stale.

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

/lifecycle stale

kubermatic-bot commented 8 months ago

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.

/lifecycle rotten

kubermatic-bot commented 5 months ago

Issues go stale after 90d of inactivity. After a furter 30 days, they will turn rotten. Mark the issue as fresh with /remove-lifecycle stale.

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

/lifecycle stale

kubermatic-bot commented 4 months ago

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.

/lifecycle rotten

kubermatic-bot commented 3 months ago

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

/close

kubermatic-bot commented 3 months ago

@kubermatic-bot: Closing this issue.

In response to [this](https://github.com/kubermatic/machine-controller/issues/1619#issuecomment-2306972817): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close 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-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
ahmedwaleedmalik commented 3 months ago

/open

ahmedwaleedmalik commented 3 months ago

@csengerszabo maybe after KKP 2.26 release we can get this prioritized somehow. It's not something urgent but would be great if we can get rid of the flakes/failures.