openstack overcloud failures|status sometimes shows incorrect output ( from deployment process)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
James Slagle |
Bug Description
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:
Changed in tripleo: | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → James Slagle (james-slagle) |
milestone: | none → stein-1 |
tags: | added: rocky-backport-potential |
Fix proposed to branch: master /review. openstack. org/605058
Review: https:/