Bug 1699260 - after deleting scap policy or deleting host itself from satellite, host still sends reports satellite/capsule.
Summary: after deleting scap policy or deleting host itself from satellite, host still...
Keywords:
Status: CLOSED DUPLICATE of bug 1662142
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: SCAP Plugin
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Jameer Pathan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-12 09:15 UTC by Jameer Pathan
Modified: 2019-04-12 15:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-12 15:07:35 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jameer Pathan 2019-04-12 09:15:41 UTC
Description of problem:
after deleting scap policy or deleting host itself from satellite, host still sends reports to satellite/capsule.

Version-Release number of selected component (if applicable):
@satellite 6.5.0 snap 23

How reproducible:
always

Steps to Reproduce:
1. have a host with scap policy assigned to it.
2. delete scap policy assigned to host or delete host itself from satellite.
3. In logs we can see that host is sending reports but those are not uploaded to satellite because policy/host itself is deleted from satellite.
# tailf -n 100 /var/log/httpd/foreman-ssl_access_ssl.log | grep "POST /api/v2/compliance/arf_reports/" 
# tailf /var/log/foreman/production.log

Actual results:
- even if scap policy or host itself is deleted from satellite even then host keeps on sending scap reports.

Expected results:
- If scap policy or host itself is deleted from satellite then host should not send scap reports to satellite.

Additional info:

Comment 3 Jameer Pathan 2019-04-12 13:52:59 UTC
found upstream issues related to this bugzilla:
https://projects.theforeman.org/issues/25763

Comment 4 Brad Buckingham 2019-04-12 15:07:35 UTC

*** This bug has been marked as a duplicate of bug 1662142 ***


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