Bug 1917506
| Summary: | Cannot delete content hosts registered before 6.9 upgrade | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Jonathon Turel <jturel> |
| Component: | Hosts | Assignee: | Jonathon Turel <jturel> |
| Status: | CLOSED NOTABUG | QA Contact: | tstrych |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.9.0 | CC: | inecas, rdesouza, ssainkar, sshtein, zhunting |
| Target Milestone: | 6.9.0 | Keywords: | Regression, Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | foreman-2.3.1.10-1 | Doc Type: | Known Issue |
| Doc Text: |
Content hosts registered prior to Satellite 6.9 upgrade cannot be deleted / unregistered; it produces the following error:
“ERROR: update or delete on table "hosts" violates foreign key constraint”.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-03-08 16:30:11 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jonathon Turel
2021-01-18 15:43:09 UTC
Created from redmine issue https://projects.theforeman.org/issues/31669 Upstream bug assigned to jturel There may be other issues fixed by this but the report we received from our user states that existing content hosts (prior to 6.9 upgrade) cannot be deleted / unregistered without getting an error like this: 2021-01-15T11:20:37 [E|bac|] PG::ForeignKeyViolation: ERROR: update or delete on table "hosts" violates foreign key constraint "fk_rails_4c747e18cb" on table "registration_facets" | DETAIL: Key (id)=(8006) is still referenced from table "registration_facets". | (ActiveRecord::InvalidForeignKey) https://community.theforeman.org/t/cant-delete-any-hosts-after-upgrade-to-katello-3-18/21998 Upstream bug assigned to jturel Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/31669 has been resolved. Hi Jonathon, can you please write me the complete reproducer steps. Firstly I would like to see the problem and then it will be reproduced with the proposed fix. I am sorry it's not clear enough to me from comment #3 Hey Tomas, sorry for the confusion here. When I first saw the user's report I thought there was a more serious issue so I immediately cloned to bugzulla. I actually think the issue is specific to their environment and the fix delivered likely does not even affect a production environment (only dev!), so I am going to close this one out as NOTABUG considering we haven't had any similar reports from downstream or upstream. |