docs: update vendor-specific metadata for oracle cloud#595
Merged
Conversation
Member
|
@smira what do you think of this |
Member
no idea, you can only test yourself and/or trust the community |
Iheanacho-ai
approved these changes
Jun 19, 2026
This addresses siderolabs/talos#12557 - thanks to @wlo2 isolating the specific issue causing boot failures, I was able to make the relevant change manually in the Oracle Cloud console and then export the updated image to inspect the metadata. The specific change is setting the `Compute.Firmware` image capability to only have `UEFI_64` as a valid value. The rest of the data added in `ImageCapabilityData` are defaults set by Oracle Cloud based on the existing template in the Talos documentation. This was validated by booting an instance with an image generated following the documentation with the addition of the two changed lines in the metadata JSON and confirming that the instance was able to boot and connected to Omni. Signed-off-by: Vidur B <vidurbutalia@gmail.com> Signed-off-by: Amarachi Iheanacho <amarachi.iheanacho@siderolabs.com>
Member
|
/m |
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
4 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.
This addresses siderolabs/talos#12557 - thanks to @wlo2 isolating the specific issue causing boot failures, I was able to make the relevant change manually in the Oracle Cloud console and then export the updated image to inspect the metadata.
The specific change is setting the
Compute.Firmwareimage capability to only haveUEFI_64as a valid value. The rest of the data added inImageCapabilityDataare defaults set by Oracle Cloud based on the existing template in the Talos documentation.This was validated by booting an instance with an image generated following the documentation with the addition of the two changed lines in the metadata JSON and confirming that the instance was able to boot and connected to Omni.
@smira I didn't know whether your reference to fixes meant an update to documentation or something else - I can see that
imagerhas test data for Oracle Cloud but it wasn't immediately apparent to me whether there was something I can contribute there. Happy to take a shot at that if there is some sort of CI pipeline that tests images against the cloud platforms that you can point me towards.