cluster-api-provider-openstack icon indicating copy to clipboard operation
cluster-api-provider-openstack copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

Missing image is hard to debug

Open lentzi90 opened this issue 1 year ago • 4 comments

/kind bug

What steps did you take and what happened:

  1. Create a cluster using an image that doesn't exist.
  2. The OpenStackCluster becomes ready (provided no bastion is used or bastion is using an existing image)
  3. There is no visible progress and no explanation for what is wrong at the OpenStackMachine level. Worse, there is a misleading message that the OpenStackMachine is waiting for bootstrap data, which is not true.
  4. There is no explanation on the OpenStackServer. It is just "not ready"

What did you expect to happen:

There should be a condition on the OpenStackServer that would propagate to the OpenStackMachine, with a message explaining that the image cannot be found. The OpenStackMachine should not say that it is waiting for bootstrap data when the data is available.

Anything else you would like to add:

This issue is also present in v0.10, just that there is no OpenStackServer involved then.

Environment:

  • Cluster API Provider OpenStack version (Or git rev-parse HEAD if manually built): v0.11.2
  • Cluster-API version: v1.8.5
  • OpenStack version:
  • Minikube/KIND version:
  • Kubernetes version (use kubectl version):
  • OS (e.g. from /etc/os-release):

lentzi90 avatar Nov 21 '24 12:11 lentzi90

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-triage-robot avatar Feb 19 '25 12:02 k8s-triage-robot

/remove-lifecycle stale

EmilienM avatar Feb 19 '25 14:02 EmilienM

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-triage-robot avatar May 20 '25 14:05 k8s-triage-robot

/remove-lifecycle stale

mnaser avatar May 20 '25 14:05 mnaser

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-triage-robot avatar Aug 18 '25 15:08 k8s-triage-robot

/remove-lifecycle stale

lentzi90 avatar Aug 19 '25 05:08 lentzi90