Bug 1691870
| Summary: | openstack overcloud delete shows user input prompt after providing input | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Marius Cornea <mcornea> |
| Component: | python-tripleoclient | Assignee: | Steve Baker <sbaker> |
| Status: | CLOSED ERRATA | QA Contact: | Sasha Smolyak <ssmolyak> |
| Severity: | urgent | Docs Contact: | |
| Priority: | high | ||
| Version: | 15.0 (Stein) | CC: | aschultz, dbecker, emacchi, hbrock, jslagle, mburns, morazi, ramishra, sbaker |
| Target Milestone: | beta | Keywords: | Triaged |
| Target Release: | 15.0 (Stein) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | python-tripleoclient-11.4.1-0.20190411190358.0ca816d.el8ost | Doc Type: | No Doc Update |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-09-21 11:20:58 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
Marius Cornea
2019-03-22 17:05:21 UTC
Removing the blocker flag, you can always run with "openstack overcloud delete --yes" If this works when manually entering 'y' as the input, and only fails when the input is scripted, then I'd suggest closing this bug and just using --yes anyway. I noticed that this is an issue with the python3 version of the command so there might be an issue in cliff or something. The issue is that the info text doesn't actually print out until after you've entered something. (undercloud) [stack@undercloud-0 ~]$ openstack stack delete overcloud Are you sure you want to delete this stack(s) [y/N]? N Verified 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/RHEA-2019:2811 |