Bug 1461563 - [RFE] Kill switch for openstack overcloud deploy
Summary: [RFE] Kill switch for openstack overcloud deploy
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: James Slagle
QA Contact: nlevinki
URL:
Whiteboard:
Depends On:
Blocks: 1480410
TreeView+ depends on / blocked
 
Reported: 2017-06-14 19:35 UTC by Andreas Karis
Modified: 2023-09-14 03:59 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1480410 (view as bug list)
Environment:
Last Closed: 2020-11-18 18:18:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Andreas Karis 2017-06-14 19:35:43 UTC
Description of problem:
We need to speed up the process for user labs. In user labs it is common that users deploy a stack, mid-way through the scheduling process or some other part of the deployment need to tear it down.

Sometimes the stack cleanup gets "hung" and can take 20 minutes or more to delete a stack (this is in OSP 10). For a lab environment where rapid development / testing is needed, this behavior is undesirable.

I would like to request a quick stack abandon feature that simply forgets about whatever was done on the overcloud nodes, pulls down the neutron ports and is done.

Comment 5 Kevin Carter 2020-11-18 18:18:50 UTC
We've simplified a lot of the components which power deployments which better enables the original ask. Specifically, with the removal of mistral in our future release, we can now mostly ^C out of a deployment execution to stop it. Given the architecture and service changes we've implemented since this RFE was created we're closing it. If there's a further need within our future release, please create a new RFE addressing the specific ask.

Comment 6 Red Hat Bugzilla 2023-09-14 03:59:13 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


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