Skip to content

Fix cluster-class naming to be 1-34.#264

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

Fix cluster-class naming to be 1-34.#264
garloff merged 1 commit intomainfrom
fix/openstack-scs2-cluster-class-1-34

Conversation

@garloff
Copy link
Copy Markdown
Member

@garloff garloff commented May 4, 2026

As reported from @schmidax:
I apparently overlooked to check-in one change of cluster class where 1-33 was remaining and 1-34 should have been ...

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
Copy link
Copy Markdown
Member Author

garloff commented May 4, 2026

Testing: openstack-scs2-1-34-v0-git-4b2b59b

@garloff garloff merged commit 9baa57c into main May 4, 2026
5 checks passed
@garloff garloff deleted the fix/openstack-scs2-cluster-class-1-34 branch May 4, 2026 08:04
@garloff
Copy link
Copy Markdown
Member Author

garloff commented May 4, 2026

cscstl does not want me to publish it :-(
Error: failed to validate with latest release hash: no change in the cluster stack

@garloff
Copy link
Copy Markdown
Member Author

garloff commented May 4, 2026

I guess I have to withdraw the old -v2 to make this work. But that might cause issues as well ...
... or I introduce some artifical cosmetic change.

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

None yet

Development

Successfully merging this pull request may close these issues.

2 participants