SovereignCloudStack / SovereignCloudStack/standards

[BUG] Test for SCS-0104 fails for other image source

Open
#1,111 11 comments 0 reactions 1 assignee View on GitHub

@fkr is already working on this.

Since Feb 26, 2026.

bug
Dominant language
Python
Stars
47
Forks
38
Avg merge
1d 16h
Merged PRs (30d)
8

Description

The source of images is checked to be with prefixes documented as examples.

We added our prefix to the test but imho the test should only validate if the source is set to a correct url.

diff --git a/Tests/iaas/scs_0104_standard_images/standard_images.py b/Tests/iaas/scs_0104_standard_images/standard_images.py
index 6f8c827..4c35cf1 100644
--- a/Tests/iaas/scs_0104_standard_images/standard_images.py
+++ b/Tests/iaas/scs_0104_standard_images/standard_images.py
@@ -13,6 +13,7 @@ _specs = yaml.safe_load(r"""
   source:
   - https://swift.services.a.regiocloud.tech/swift/v1/AUTH_b182637428444b9aa302bb8d5a5a418c/openstack-k8s-capi-images/ubuntu-2404-kube
   - https://swift.services.a.regiocloud.tech/swift/v1/AUTH_b182637428444b9aa302bb8d5a5a418c/openstack-k8s-capi-images/ubuntu-2204-kube
+  - https://repo.uhurutec.io/content/umetal/k8s-node-images
 "ubuntu-capi-image-2":
   # this name_scheme uses `-` to separate base name "ubuntu-capi-image" from version
   # latest openstack-image-manager can be told to use `-` by setting `separator: "-"` on the image
@@ -20,6 +21,7 @@ _specs = yaml.safe_load(r"""
   source:
   - https://swift.services.a.regiocloud.tech/swift/v1/AUTH_b182637428444b9aa302bb8d5a5a418c/openstack-k8s-capi-images/ubuntu-2404-kube
   - https://swift.services.a.regiocloud.tech/swift/v1/AUTH_b182637428444b9aa302bb8d5a5a418c/openstack-k8s-capi-images/ubuntu-2204-kube
+  - https://repo.uhurutec.io/content/umetal/k8s-node-images
 "Ubuntu 24.04":
   source:
   - https://cloud-images.ubuntu.com/releases/noble/

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.