Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: properly handle upgrades for the machines with invalid schematics #77

Merged
merged 1 commit into from
Mar 18, 2024

Conversation

Unix4ever
Copy link
Member

@Unix4ever Unix4ever commented Mar 18, 2024

Simple fix to not skip updating Talos if the machine schematic is empty.

Verified that on a cluster running on the nodes with the invalid schematics. Upgrades work.

Simple fix to not skip updating Talos if the machine schematic is empty.

Signed-off-by: Artem Chernyshev <[email protected]>
@@ -129,7 +129,7 @@ func NewClusterMachineConfigStatusController() *ClusterMachineConfigStatusContro
machineStatus.TypedSpec().Value.Schematic.Id != expectedSchematic

// don't run the upgrade check if the running version and expected versions match
if versionMismatch && talosVersion.TypedSpec().Value.TalosVersion != "" && talosVersion.TypedSpec().Value.SchematicId != "" {
if versionMismatch && talosVersion.TypedSpec().Value.TalosVersion != "" {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how does it work with "invalid" schematics? is it going to wipe it?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, it's going to keep using the vanilla installer.
This code is in place, but this check made it skip the upgrade function as a whole.

@Unix4ever
Copy link
Member Author

/m

@talos-bot talos-bot merged commit 2d1b776 into main Mar 18, 2024
18 checks passed
@talos-bot talos-bot deleted the fix-upgrade-invalid-schematics branch March 18, 2024 14:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants