| Summary: | Hostgroup with rules is not prevented from deletion | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Lukas Zapletal <lzap> |
| Component: | Discovery Plugin | Assignee: | Lukas Zapletal <lzap> |
| Status: | CLOSED ERRATA | QA Contact: | Sachin Ghai <sghai> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.2.0 | CC: | bbuckingham, cwelton, sghai |
| Target Milestone: | Unspecified | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://projects.theforeman.org/issues/11574 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-07-27 09:24:25 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: | |
|
Description
Lukas Zapletal
2016-03-02 07:58:36 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/11574 has been closed ------------- Anonymous Applied in changeset commit:foreman_discovery|82d93bfb7748482ca32ab293d8c0b47c38c4c018. Verified with sat6.2 snap3.
Now if user try to delete a hostgroup which is associated to discovery rule, User will see proper error:
2016-03-10 13:21:39 [app] [I] Started DELETE "/hostgroups/1-sat_rhel7_hg" for 10.65.193.200 at 2016-03-10 13:21:39 +0100
2016-03-10 13:21:39 [app] [I] Processing by HostgroupsController#destroy as HTML
2016-03-10 13:21:39 [app] [I] Parameters: {"authenticity_token"=>"+e1GaMx9dDLPcz9e30jXEgMW+e0ROv6fozQCV3N8BlU=", "id"=>"1-sat_rhel7_hg"}
2016-03-10 13:21:40 [app] [I] Failed to save: Cannot delete record because dependent discovery rules exist
2016-03-10 13:21:40 [app] [I] Redirected to https://ibm-x3550m3-07.lab.eng.brq.redhat.com/hostgroups
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, 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/RHBA-2016:1501 |