RHEL 8 patching failure

1

Hi Guys,

We faced an issue while deploying the Kernel patch on one RHEL 8 system, below is the edr log:

66138 : 2021-02-07 10:15:46 : INFO : Start Task ID: 281887
66138 : 2021-02-07 10:15:46 : INFO : RHEL-Patch-Client at version 3.0.1.0
66138 : 2021-02-07 10:15:46 : INFO : 01 setup and request repomd.xml
66138 : 2021-02-07 10:15:46 : INFO : dnf cache lock is not expired yet. Skip repomd.xml file requests.
66138 : 2021-02-07 10:15:46 : INFO : dnf cache lock is not expired yet. Skip repomd.xml file requests.
66138 : 2021-02-07 10:15:46 : INFO : dnf cache lock is not expired yet. Skip repomd.xml file requests.
66140 : 2021-02-07 10:15:47 : INFO : 03 lock repo data
66142 : 2021-02-07 10:15:47 : INFO : 04 dependency resolution and request packages
66142 : 2021-02-07 10:15:47 : INFO : Download Plugin mode.
66142 : 2021-02-07 10:15:47 : WARNING : Skip old rpms.
66142 : 2021-02-07 10:15:47 : WARNING : Before skip: 1
66142 : 2021-02-07 10:15:47 : WARNING : After skip: 0
66142 : 2021-02-07 10:15:47 : INFO : Run cmd: env: {} cmd: dnf --verbose --cacheonly -c /var/opt/BESClient/EDRDeployData//EDR_Dnfconfig_281887 bf_dependency_resolution --skip-broken --assumeyes
66142 : 2021-02-07 10:15:47 : INFO : Set timout: 45 seconds
66142 : 2021-02-07 10:15:49 : ERROR : Dependency resolution failed.
66142 : 2021-02-07 10:15:49 : ERROR : No packages are available.
66142 : 2021-02-07 10:15:49 : ERROR : Exit Code: 201
Loaded plugins: bf_dependency_resolution
DNF version: 4.2.23
cachedir: /var/opt/BESClient/rhsmdnf/cache
User-Agent: constructed: 'libdnf (Red Hat Enterprise Linux 8.3; generic; Linux.x86_64)'
repo: using cache for: RedHatEnterpriseLinux8forx8664AppStreamRPMs
RedHatEnterpriseLinux8forx8664AppStreamRPMs: using metadata from Tue Feb 2 13:40:14 2021.
repo: using cache for: RedHatEnterpriseLinux8forx8664BaseOSRPMs
RedHatEnterpriseLinux8forx8664BaseOSRPMs: using metadata from Tue Feb 2 13:35:54 2021.
repo: using cache for: RedHatEnterpriseLinux8forx8664SupplementaryRPMs
RedHatEnterpriseLinux8forx8664SupplementaryRPMs: using metadata from Tue Dec 15 21:42:07 2020.
Last metadata expiration check: 1 day, 19:00:47 ago on Fri Feb 5 15:15:00 2021.
–> Starting dependency resolution
–> Finished dependency resolution

66146 : 2021-02-07 10:15:49 : ERROR : dnf command not continue, last command exit code is not 0
[Sun, 07 Feb 2021 10:15:49 +0530] 281884 Warning: Nothing to install. Please check if you are using the latest kernel.
[Sun, 07 Feb 2021 10:15:49 +0530] 281885 Warning: Nothing to install. Please check if you are using the latest kernel.

Can some one help me in resolving the issue?

Thanks in advance.

2

On the targeted endpoint, what’s the non-0 return code in the EDR data directory under the BESClient (default path is /var/opt/BESClient on Linux)?

Another option is to utilize my YUM-Check content to analyze and remediate any YUM issues that could be interfering with your RHEL patch deployments via BigFix.

Here are some documentation links that should prove to be helpful.

3

Hi @cmcannady the exit code is 201 which is there in the logs which i have shared.

4

Hi,

Have you checked whether same kernel already installed or not. ?

1 Like
5

Hi @sekar yes we have checked the same kernel is not installed.

6

Hi ,

Have deployed below fixlet and client setting before patching ? if not deploy and change setting before deployment then restart client service

Fixlet ID : Import RPM-GPG-KEY-redhat-release - RHEL 8

“_BESClient_ActionManager_PrefetchPlugInTimeoutSeconds”=“1800"
”_BESClient_RHEL_AllowYumDownloads=0"

1 Like
7

You’re right, I missed that from your initial post. If the RHEL pre-req fixlet and suggested client settings by @sekar don’t help, I’d recommend trying my YUM-Check content to analyse your CentOS/RHEL endpoints for issues and remediate accordingly.

If both of these steps don’t resolve your issues, then you’ll have to enable BESClient debug logging at log-level 10k and then open a support case with our L2 team for additional troubleshooting efforts.

8

The issue was resolved after multiple of reboots of the system and deploying latest kernel patch which was released.

9

I reviewed you BES actions and Analysis and they all error out when executing them. During the import process or just executing them from windows explorer, Can you tell me how to fix this?

2023-02-22_09-22-09

10

That’s likely a problem in how the files were saved out of GitHub. Can you paste the first 10 lines of the file you saved here?

1 Like
11

Thanks Jason,
There is a lot of code in this.

<!DOCTYPE html>
<html lang="en" data-color-mode="auto" data-light-theme="light" data-dark-theme="dark" data-a11y-animated-images="system">
  <head>
<meta charset="utf-8">
  <link rel="dns-prefetch" href="https://github.githubassets.com">
  <link rel="dns-prefetch" href="https://avatars.githubusercontent.com">
  <link rel="dns-prefetch" href="https://github-cloud.s3.amazonaws.com">
  <link rel="dns-prefetch" href="https://user-images.githubusercontent.com/">
  <link rel="preconnect" href="https://github.githubassets.com" crossorigin>
  <link rel="preconnect" href="https://avatars.githubusercontent.com">
12

Yeah, I think it saved the whole GitHub HTML page, not the file that was displayed. It should have been the XML.

1 Like
13

I have a post for “how to download files from GitHub” with screenshots at Tips: Downloading files from GitHub

1 Like
14

You need to download the “RAW” version as what’s displayed in your browser has a lot of markup, etc. Please see following screenshot.

image
image1262Ă—570 48.4 KB

That will take you to >> Troubleshooting - Yum Check - Output