Bug 1129727
Summary: | staypuft: user can delete a running deployment without stopping it first | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Dafna Ron <dron> | ||||
Component: | rubygem-staypuft | Assignee: | Mike Burns <mburns> | ||||
Status: | CLOSED EOL | QA Contact: | Omri Hochman <ohochman> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | unspecified | CC: | mburns, pasik, srevivo | ||||
Target Milestone: | --- | Keywords: | ZStream | ||||
Target Release: | Installer | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2016-09-29 13:27:36 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: | |||||||
Attachments: |
|
Closing list of bugs for RHEL OSP Installer since its support cycle has already ended [0]. If there is some bug closed by mistake, feel free to re-open. For new deployments, please, use RHOSP director (starting with version 7). -- Jaromir Coufal -- Sr. Product Manager -- Red Hat OpenStack Platform [0] https://access.redhat.com/support/policy/updates/openstack/platform |
Created attachment 926467 [details] log Description of problem: we can delete a running deployment and succeed. i think a running deployment should be stopped first or a force delete should be used. Version-Release number of selected component (if applicable): ruby193-rubygem-staypuft-0.2.2-1.el6ost.noarch How reproducible: 100% Steps to Reproduce: 1. start a deployment 2. delete the deployment while its still running 3. Actual results: we succeed to delete the deployment Expected results: we should not succeed to delete the deployment before stopping it or we need to use a --force to delete a running deployment Additional info: