Bug 2150371
| Summary: | Removing CV error's with "Cannot delete record because of dependent content_facet" | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | tharring |
| Component: | Content Views | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED MIGRATED | QA Contact: | Satellite QE Team <sat-qe-bz-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.11.3 | CC: | ankulkar, sajha, wclark |
| Target Milestone: | Unspecified | Keywords: | MigratedToJIRA, Triaged, WorkAround |
| Target Release: | Unused | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-06-06 12:55:51 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
tharring
2022-12-02 17:45:23 UTC
If anybody else runs into this issue, it seems that the bug is that the Host was removed somehow without removing its associated ContentFacet. Logs of the original removal of the Host would be helpful to better understand the issue. We have added a foreman-rake task clean_orphaned_facets to deal with this. That was part of the fix of a different BZ with the same root cause. https://bugzilla.redhat.com/show_bug.cgi?id=2147579. We can probably add some information when CV delete fails due to an orphaned content host in the system. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |