csctl confused on several releases in one OCI repository

Ouverte
#220 7 commentaires 0 réactions 3 personnes assignées Voir sur GitHub

@jschoone y travaille déjà.

Depuis le 24/4/2026.

  • #221 par @garloff — ouverte

Évaluation

Cette issue n'a pas encore été évaluée.

Description

Container

/kind bug

What steps did you take and what happened:
Trying to publish an scs2 cluster-stack release

export OCI_REGISTRY=registry.scs.community
export OCI_REPOSITORY=$OCI_REGISTRY/kaas/cluster-stacks
export OCI_USERNAME='robot$REDACTED'
OCI_PASSWORD="REDACTED" \
  csctl create -m stable --publish --remote oci providers/openstack/scs2

gives me

path "providers/openstack/scs2": cluster stack hash: "vwlbjtw3nnhtire1qx7ffo9a8v8qpkditzy2svv4knw"
Error: failed to create create options: failed to get latest release form remote repository: failed to get match release tag "openstack-hosted-control-plane-1-34-v0-sha-0ewkztd" with spec of ClusterStack: failed to get clusterstack object from string "openstack-hosted-control-plane-1-34-v0-sha-0ewkztd": invalid forma

There is no trace of anything hosted-control-plane that I want to publish.
Nevertheless, csctl barfs on it -- probably based on what it finds on the registry, which it looks at to determine the version, I guess ...

[A clear and concise description of what the bug is.]

csctl should not care about openstack-hosted-cotrol-plane when I try to publish openstack-scs2
providers/openstack/scs2/csctl.yaml:

garloff@dev2018(://):/casa/src/SCS/cluster-stacks [1]$ cat providers/openstack/scs2/csctl.yaml
apiVersion: csctl.clusterstack.x-k8s.io/v1alpha1
config:
  clusterStackName: scs2
  kubernetesVersion: v1.33.10
  provider:
    apiVersion: openstack.csctl.clusterstack.x-k8s.io/v1alpha1
    type: openstack

What did you expect to happen:

csctl to determine what version to assign to my openstack-scs-1-33 (v5, I guess) and push it out.

Anything else you would like to add:
This prevents me from publishing openstack-scs2-1-33-v5 (k8s-v1.33.10, https://github.com/SovereignCloudStack/cluster-stacks/pull/260) and openstack-scs2-1-34-v2 (k8s-v1.34.7, https://github.com/SovereignCloudStack/cluster-stacks/pull/261).

Environment:

csctl version:
csctl version: dev
commit: unknown

(this was built from git 800cac63e6adf4a1b6cd33da44b637df9e83bd2e, last commit from Dec 31, 2025)
Side question: Should I open a separate bug on csctl's inability to report its own version?

Langage dominant
Go
Étoiles
3
Forks
1
Métriques de merge des PR
Aucune PR mergée en 30 j

Préparer son environnement

  • Aucun Dockerfile ni fichier Docker Compose
  • Propose un modèle de pull request
  • Aucun guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de SovereignCloudStack/csctl

Toutes les issues de SovereignCloudStack/csctl

Issues similaires

Plus d'issues Go

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.