Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be unavailable on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1127302 - staypuft: can't remove a deployment that has hosts assigned
Summary: staypuft: can't remove a deployment that has hosts assigned
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rubygem-staypuft
Version: 5.0 (RHEL 7)
Hardware: x86_64
OS: Linux
Target Milestone: z2
: Installer
Assignee: Mike Burns
QA Contact: Omri Hochman
Depends On:
TreeView+ depends on / blocked
Reported: 2014-08-06 15:06 UTC by Dafna Ron
Modified: 2014-12-15 09:46 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-11-04 18:13:54 UTC
Target Upstream Version:

Attachments (Terms of Use)
screen shot (108.87 KB, image/png)
2014-08-06 15:06 UTC, Dafna Ron
no flags Details

Description Dafna Ron 2014-08-06 15:06:25 UTC
Created attachment 924516 [details]
screen shot

Description of problem:

when I try to remove a deployment which has hosts assigned to it I get an error: 

Cannot delete record because it has descendants.

I think that this looks really bad from user prospective and we should be able to remove the hosts from the deployment when the user approves it. 
which is why I think we need to add a pop-up with a warning + approve/cancel operation. 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. create a new deployment and assign hosts to the deployment
2. try to remove the deployment 

Actual results:

we get this error: 
Cannot delete record because it has descendants.

Expected results:

1. this looks like a UI crash 
2. we should be able to complete this action with user approval (detaching the hosts from the deployment ourselves) 

Additional info: look at screen shot - not very user friendly and looks like crash. 

Cannot delete record because it has descendants.
app/models/concerns/foreman/thread_session.rb:33:in `clear_thread'
lib/middleware/catch_json_parse_errors.rb:9:in `call'

Comment 3 Alexander Chuzhoy 2014-10-31 14:22:16 UTC


Was able to remove the deployment after assinging hosts to it.

Comment 4 Scott Lewis 2014-11-04 18:13:54 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, and where to find the updated
files, follow the link below.

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


Note You need to log in before you can comment on or make changes to this bug.