Custom Software Source Creation Fails
Creating a custom or versioned custom software source might fail if you include too many packages, include packages that aren't in the base vendor software sources, or if the custom software source is unable to resolve package dependencies.
Review job error logs
To identify the reason for the custom software source failure, review the error logs for the job.
- Open the navigation menu and click Observability & Management. Under OS Management Hub, click Jobs.
- Under List scope, select the compartment associated with the job.
- Click the Completed jobs tab.
-
Under Filters, select the following:
- Status: Failed
- Type: Create software source or Update software source
- Click the name of the job.
- Under Resources, click Error messages.
Large number of packages
Custom software sources that contain too many packages remain in the 'Creating' state for a long period and then fail.
Limit packages to 90,000 or less. To reduce the number of packages, use filters, a package list, or reduce the number of vendor software sources included in the source. If you need more packages than the limit, create multiple custom software sources each with a smaller number of packages.
Unsupported packages included
Some packages don't exist in any of the vendor software sources and can't be included in a custom software source. Don't include any of the following packages in a custom software source:
- gpg-pubkey
- unified-monitoring-agent
- wlp-agent
Missing vendor software sources
The custom software source must contain all vendor software sources needed for the packages that you include. If you've selected the auto-resolve dependencies option, you must also include all necessary vendor software sources for the dependent packages. Verify that you've selected all necessary vendor software sources when creating the custom or version software source.
If you're unsure which vendor software source a package requires, you can search for the package and identify the software source.