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

Omni: duplicate machine UUID problem #38

Open
1 of 2 tasks
smira opened this issue Sep 1, 2023 · 2 comments
Open
1 of 2 tasks

Omni: duplicate machine UUID problem #38

smira opened this issue Sep 1, 2023 · 2 comments

Comments

@smira
Copy link
Member

smira commented Sep 1, 2023

Talos: use by default SMBIOS UUID, but it there's a META key with UUID override, use that value.

Omni: if the machine joins with known bad UUID, Omni established "temporary" SideroLink connection, updates META value via Talos API with random generated UUID, and the machine re-joins with new random UUID.

Tasks

Preview Give feedback
  1. DmitriyMV
@smira smira transferred this issue from another repository Mar 4, 2024
@smira smira transferred this issue from siderolabs/omni-issue-mover Mar 4, 2024
@fstaffa
Copy link

fstaffa commented Jan 2, 2025

@smira I am facing this problem with Zimaboard and Omni. Is there a workaround/fix? I tried setting talos.config kernel parameter (https://www.talos.dev/v1.9/reference/kernel/#talosconfig) , but either I got it wrong or it is ignored.

@smira
Copy link
Member Author

smira commented Jan 8, 2025

This is not implemented in Omni (yet), but you could try to build a Talos installation media from Omni providing a META value 0xe=<other UUID> which should override the UUID provided by SMBIOS.

Sometimes hardware vendors have firmware updates fixing the issue.

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

No branches or pull requests

2 participants