Skip to content

Improved wording suggesting SCS-2V-4-20s for control plane.#265

Merged
garloff merged 1 commit intomainfrom
fix/openstack-scs2-cluster-class-1-34.v2
May 4, 2026
Merged

Improved wording suggesting SCS-2V-4-20s for control plane.#265
garloff merged 1 commit intomainfrom
fix/openstack-scs2-cluster-class-1-34.v2

Conversation

@garloff
Copy link
Copy Markdown
Member

@garloff garloff commented May 4, 2026

The real reason for this change is to be able to publish something new.

See #264 (comment)

The real reason for this change is to be able to publish something new.

Signed-off-by: Kurt Garloff <kurt@garloff.de>
@garloff garloff self-assigned this May 4, 2026
@garloff garloff added bug Something isn't working Container Issues or pull requests relevant for Team 2: Container Infra and Tooling labels May 4, 2026
@garloff garloff merged commit a931cdb into main May 4, 2026
5 checks passed
@garloff garloff deleted the fix/openstack-scs2-cluster-class-1-34.v2 branch May 4, 2026 15:15
@github-project-automation github-project-automation Bot moved this from Backlog to Done in Sovereign Cloud Stack May 4, 2026
@garloff
Copy link
Copy Markdown
Member Author

garloff commented May 4, 2026

And csctl still hates me. The hashing comparison does not seem to include the cluster-class contents.

csctl create -m stable --publish --remote oci providers/openstack/scs2
path "providers/openstack/scs2": cluster stack hash: "azlfam7rgn823z07ougej26xmpzsohlj0tvr4s0njis"
latest release found: "openstack-scs2-1-34-v2"
ClusterAddon Version unchanged: v2
NodeImage Version unchanged: v1
Error: failed to validate with latest release hash: no change in the cluster stack

Yeah, nodeImage and clusterAddons did not change. But the clusterClass did ... Why is it not compared?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working Container Issues or pull requests relevant for Team 2: Container Infra and Tooling

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants