Bug 1860422

Summary:	Host with remediations can't be removed
Product:	Red Hat Satellite	Reporter:	Mirek Długosz <mzalewsk>
Component:	RH Cloud - Inventory	Assignee:	Shimon Shtein <sshtein>
Status:	CLOSED ERRATA	QA Contact:	Mirek Długosz <mzalewsk>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.7.0	CC:	aruzicka, gpayelka, kupadhya, pcreech, pdudley, pgustafs
Target Milestone:	6.8.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-foreman_rh_cloud-2.0.10	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-27 13:04:32 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mirek Długosz 2020-07-24 14:10:33 UTC

If host has any remediations (obtained by "Sync" on Insights page), it can't be removed from Satellite. Following error message is displayed:

PG::ForeignKeyViolation: ERROR: update or delete on table "hosts" violates foreign key constraint "fk_rails_864b02d191" on table "insights_hits" DETAIL: Key (id)=(4) is still referenced from table "insights_hits". : DELETE FROM "hosts" WHERE "hosts"."id" = $1


Steps to Reproduce:
1. Register client to Satellite and Insights. Ensure that host will violate at least one Insights rule (so recommendation will be available for this host)
2. Set up Satellite RH Cloud - Inventory plugin so it can sync hits data from cloud
3. Go to Configure -> Insights and click "Sync"
4. Go to Hosts -> All Hosts and try to delete host from step 1


Actual results:
Error message is displayed:
"PG::ForeignKeyViolation: ERROR: update or delete on table "hosts" violates foreign key constraint "fk_rails_864b02d191" on table "insights_hits" DETAIL: Key (id)=(4) is still referenced from table "insights_hits". : DELETE FROM "hosts" WHERE "hosts"."id" = $1"


Expected results:
Host is removed from Satellite


Found on:
Satellite 6.7.2 snap 2
katello-3.14.0-6.el7sat.noarch
satellite-6.7.2-1.el7sat.noarch
foreman-1.24.1.24-1.el7sat.noarch
pulp-server-2.21.0.1-1.el7sat.noarch
tfm-rubygem-foreman_rh_cloud-1.0.9-1.el7sat.noarch

Comment 3 Adam Ruzicka 2020-08-12 13:00:32 UTC

*** Bug 1864058 has been marked as a duplicate of this bug. ***

Comment 4 Mirek Długosz 2020-09-02 12:39:34 UTC

Host with remediations can be removed, tested by following steps from initial report.


Tested on:
Satellite 6.8 snap 13
pulp-server-2.21.2-1.el7sat.noarch
foreman-2.1.2.1-1.el7sat.noarch
katello-3.16.0-0.4.rc4.el7sat.noarch
satellite-6.8.0-1.el7sat.noarch
tfm-rubygem-foreman_rh_cloud-2.0.10-1.el7sat.noarch

Comment 5 Mirek Długosz 2020-09-07 10:34:49 UTC

*** Bug 1875966 has been marked as a duplicate of this bug. ***

Comment 10 errata-xmlrpc 2020-10-27 13:04:32 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.8 release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:4366