Bug 1263514
Summary: | Deleting a compute resource/profile does not cascade delete ids from hosts table | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Chris Roberts <chrobert> |
Component: | Infrastructure | Assignee: | satellite6-bugs <satellite6-bugs> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | Nightly | CC: | adprice, bbuckingham, chrobert, cwelton, sshtein, xdmoon |
Target Milestone: | Unspecified | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
URL: | http://projects.theforeman.org/issues/12982 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-09-12 20:49:44 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
Chris Roberts
2015-09-16 03:38:57 UTC
Created redmine issue http://projects.theforeman.org/issues/12982 from this bug Upstream bug component is Provisioning What behavior is desired? I can prevent the action from actually removing compute profile/resource until all hosts are disassociated from it. If I try to disassociate hosts automatically we will encounter a problem when the user is authorized to delete a resource, but is not authorized to see all hosts that use this resource (for example those hosts belong to a different org/loc). In this case I will either change objects (hosts) that the user is authorized to, or I still will be unable to complete the action. Same issue exists for any resource connected to a host like hostgroup, puppet environment e.t.c. IMHO, the best action here will be validation and reject while there are hosts connected to it. Shimon, I agree with this action: IMHO, the best action here will be validation and reject while there are hosts connected to it. - Chris Looks like https://bugzilla.redhat.com/show_bug.cgi?id=1207972 should fix this issue too. I can see that in upstream it's already fixed. Upstream bug component is Infrastructure Upstream bug component is Provisioning Upstream bug component is Infrastructure Upstream bug component is Infrastructure |