Hi team,
Can help on this. As support we already have OEL plugin and custom repository which I pointing to our local repository server.
When I try yum update we can see the packages are coming from the repository but when use the bigfix baselines/fixlets which all the packages are getting failing and EDR logs shows dependency resolution failed and repo is empty but the server is already configured with repository and getting packages strange.
Do I understand correctly that you do not want to use the vendor package repository, and you do want to use your local on-prem package repository ?
If yes, you need to configure the client to use the custom repository with the following Fixlets. Enable when you want to use custom package repositories, and disable when you want to use the vendor package repositories.
Hi,
Yes, we have local repository server that is syncing with internet oracle server and save the packages on our local repository server. We already using OEL 8 without any issue. Also the same repository configuration is already configured on bigfix console on “custom repository section”
Now we started to use OEL 9 however all the packages are getting failed as below errors on EDR logs,
113641 : 2025-10-23 16:44:08 : INFO : Start Task ID: 1956539
113641 : 2025-10-23 16:44:08 : INFO : OEL-Patch-Client at version 3.0.3.0
113641 : 2025-10-23 16:44:08 : INFO : 01 setup and request repomd.xml
113641 : 2025-10-23 16:44:08 : WARNING : Repo list is empty for OS: oel-9-x64
113643 : 2025-10-23 16:44:08 : INFO : 03 lock repo data
113645 : 2025-10-23 16:44:09 : INFO : 04 dependency resolution and request packages
113645 : 2025-10-23 16:44:09 : WARNING : Repo list is empty for OS: oel-9-x64
113645 : 2025-10-23 16:44:09 : INFO : Download Plugin mode.
113645 : 2025-10-23 16:44:09 : INFO : Run cmd: env: {} cmd: dnf --verbose --cacheonly -c /var/opt/BESClient/EDRDeployData//EDR_Dnfconfig_1956539 bf_dependency_resolution --assumeyes xfsprogs-6.12.0-1.0.2.el9.x86_64
113645 : 2025-10-23 16:44:09 : INFO : Set timout: 45 seconds
113645 : 2025-10-23 16:44:09 : ERROR : Dependency resolution failed.
113645 : 2025-10-23 16:44:09 : ERROR : Exit Code: 1
Loaded plugins: bf_dependency_resolution
DNF version: 4.14.0
cachedir: /var/opt/BESClient/oelr2dnf/cache
User-Agent: constructed: ‘libdnf (Oracle Linux Server 9.5; server; Linux.x86_64)’
Error: No match for argument: xfsprogs-6.12.0-1.0.2.el9.x86_64
This is the sample for local repo server configured for OEL 8 and OEL 9,
Oracle Linux 8 Add Ons
Oracle Linux 8 Base OS
Oracle Linux 8 UEKR6
Oracle Linux 8 UEKR7
Oracle Linux 8 Appstream
You have not confirmed that you used the Fixlet that I posted to configure the client to use custom repos.
That Fixlet adds the client setting “_BESClient_OEL_AllowYumDownloads”=“1”
For OL8 we only support on-prem custom repositories, there is no other choice.
For OL9 we support both vendor provided repositories and on-prem custom repositories, with the vendor repositories being the default.
In you case the client is trying to download the repository metadata, perform dependency checks with this metadata, and then download the packages from the vendor.
As you do not want to do this, you need to change the default behavior by adding the client setting using the Fixlet that I shared.