Update MAC address and UUID generation logic#10
Merged
Conversation
yordangit
requested review from
agonzalezrh,
fridim,
rut31337,
stencell and
wkulhanek
as code owners
YoNoSoyVictor
approved these changes
Mar 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix deterministic UUID/MAC collision across concurrent provisions
The seed for random firmware UUID and MAC address used only the
instance name (e.g. "bastion"), producing identical values for every
deployment. This caused Satellite registration failures because all
bastion VMs shared the same system identity UUID, and the first
registered consumer blocked all subsequent registrations with
RestlibException.
Add guid to the seed so each deployment generates unique values while
preserving idempotency for re-runs of the same deployment.