Bug 1632222
| Summary: | [OSP14] openstack overcloud failures|status sometimes shows incorrect output ( from deployment process) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Artem Hrechanychenko <ahrechan> | ||||||
| Component: | python-tripleoclient | Assignee: | James Slagle <jslagle> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Gurenko Alex <agurenko> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 14.0 (Rocky) | CC: | hbrock, jslagle, mburns, ohochman | ||||||
| Target Milestone: | beta | Keywords: | Triaged | ||||||
| Target Release: | 14.0 (Rocky) | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | python-tripleoclient-10.5.1-0.20180906012843.el7ost | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2019-01-11 11:53:20 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: |
|
||||||||
Created attachment 1486384 [details]
screens[2]
python-tripleoclient-10.5.1-0.20180901082351.6d7aa74.el7ost.noarch.rpm VERIFIED python-tripleoclient-10.6.1-0.20181010222410.8c8f259.el7ost.noarch 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:0045 |
Created attachment 1486383 [details] screens Description of problem: I logged into env from two ssh terminals: in one terminal I run opentack overcloud failures twice. first attempt - failed by timeout after that I run it again. in another terminal I run script for re-deployment of overcloud. and as you can see from screen[1]: at first terminal where I run openstack failures list I see part of stdout in "tail -F mode" from another terminal where I run overcloud deploy The same situation for openstack overcloud status Version-Release number of selected component (if applicable): How reproducible: if runs openstack overcloud commands in parallel with overcloud deployments Steps to Reproduce: 1. start overcloud deployment 2. open new terminal and run openstakc overcloud status or overcloud failures Actual results: output from overcloud deployment instead of failures or overcloud status Expected results: failures or overcloud status Additional info: