Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1690251 - Kernel updated from tower for the Host still show as detected issues on Insights Portal. [NEEDINFO]
Summary: Kernel updated from tower for the Host still show as detected issues on Insig...
Status: NEW
Alias: None
Product: Red Hat Insights
Classification: Red Hat
Component: Pilot
Version: unspecified
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Rob Williams
QA Contact: Rob Williams
Kevin Blake
Depends On:
TreeView+ depends on / blocked
Reported: 2019-03-19 07:03 UTC by Sagar Lutade
Modified: 2019-03-25 20:13 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:
robwilli: needinfo? (slutade)

Attachments (Terms of Use)

Description Sagar Lutade 2019-03-19 07:03:25 UTC
Description of problem:

Kernel updated on the host using tower still shows Detected Issues on the insights portal.

Version-Release number of selected component (if applicable):


How reproducible:

Register the host to insights and create planner playbook to fix the issues.

Steps to Reproduce:
1. Register the host to Insights.

   # insights-client --register

2. On the Portal create the Planner for the host (

3. Sync the insights-inventory on the Tower.

4. Run the playbook and select the planner playbook created on the portal to remediate the host.

5. Check if there is any kernel update.
   # yum udpate kernel                  ======> There shouls not be any update.

6. Run the insights-client to upload the latest results.
   # insights-client

7. Login to the Portal > Inventory > Host > Configuration Assessment > This should not show the kernel vulnerabilities.

Actual results:

Detected Issues
This machine is vulnerable because it runs a vulnerable kernel.

Expected results:

Their vulnerability must show as fixed.

Additional info:

Let me know if this method is correct from the tower point of view.

Comment 1 Rob Williams 2019-03-25 20:11:32 UTC
Hi Sagar,
To help narrow in on the underlying problem potentially occurring here, can you please provide the following details:

- Which registered host of yours is encountering this problem (Please provide at least 1 hostname)
- Which rules are appearing for that host/s that that you do not feel should be appearing anymore.

This level of detail will be helpful to help for any further investigation.

Note You need to log in before you can comment on or make changes to this bug.