OSMH best practice for validating package lists and dependencies Versioned Custom Software Sources
Hello,
I am creating Versioned Custom Software Sources in OCI OS Management Hub using Terraform with content_mode = "PACKAGE_LIST".
The package lists are generated from Oracle Linux 8 x86_64 instances using:
dnf update --assumeno --refresh
The final list is converted to NVRA format and associated with several Oracle Linux vendor software sources, including:
- BaseOS
- AppStream
- Addons
- OCI Included
- Ksplice
- UEK R6/R7
- Developer EPEL
When Terraform creates the Software Source, OCI rejects some packages with:
These packages are not in any of the vendor software sources chosen
Could not resolve dependencies for the packages in the software source.
nothing provides python3-importlib-metadata
Tagged:
0