search

siderolabs / omni

SaaS-simple deployment of Kubernetes - on your own hardware.
Other
402 stars 23 forks source link

ERROR Pulling Image: official extension "siderolabs/talos-vmtoolsd" is not available for Talos version v1.7.1 #215

Closed RvRuttenFS closed 1 month ago

RvRuttenFS commented 2 months ago

Updating the Omni Cluster Template to use v1.7.1 worked fine - syncing was done successfully. But the nodes could not pull correctly from image-factory.

From the Machine log:

03/05/2024 15:22:51
[talos] validating "factory.talos.dev/installer/35913d421bb9111c2a63f0c5710b9c090c168c3c9736477d445792a6a8d15d39:v1.7.1"
03/05/2024 15:22:51
[talos] retrying error: failed to pull image "factory.talos.dev/installer/35913d421bb9111c2a63f0c5710b9c090c168c3c9736477d445792a6a8d15d39:v1.7.1": failed to resolve reference "factory.talos.dev/installer/35913d421bb9111c2a63f0c5710b9c090c168c3c9736477d445792a6a8d15d39:v1.7.1": unexpected status from HEAD request to https://factory.talos.dev/v2/installer/35913d421bb9111c2a63f0c5710b9c090c168c3c9736477d445792a6a8d15d39/manifests/v1.7.1: 400 Bad Request

Error message when I put that url in the browser:

error enhancing profile from schematic: official extension "siderolabs/talos-vmtoolsd" is not available for Talos version v1.7.1

smira commented 2 months ago

I'm not sure where this name even came from, there's no such extension.

The proper name is siderolabs/vmtoolsd-guest-agent.

There's no bug in the Image Factory per se, moving to Omni.

Unix4ever commented 2 months ago

Is addressed in #205