Bug 1911269

Summary: waiting for the build message present when build exists
Product: OpenShift Container Platform Reporter: Debsmita Santra <dsantra>
Component: Dev ConsoleAssignee: Debsmita Santra <dsantra>
Status: CLOSED ERRATA QA Contact: Aritra Roy <ariroy>
Severity: low Docs Contact:
Priority: medium    
Version: 4.7CC: aballant, aos-bugs, ariroy, nmukherj, rorai
Target Milestone: ---Keywords: UpcomingSprint
Target Release: 4.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-24 15:49:10 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:

Description Debsmita Santra 2020-12-28 12:47:05 UTC
Description of problem:
The "waiting for the build" message is showing up whenever the deployment is scaling up even when a build has already completed.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. go to +Add => from git
2. enter git url
3. complete the form
4. wait for the first build to complete
5. select node in topology
6. go to details tab and scale up from 1 to 3 pods
7. go to resource tab

Actual results:
"waiting for builds" info message appears while a build is present.

Expected results:
"waiting for builds" info message should not appear while a build is present.

Additional info:

Comment 2 Rohit Rai 2021-01-27 09:28:54 UTC
verified on build 4.7.0-0.nightly-2021-01-26-162323

Comment 5 errata-xmlrpc 2021-02-24 15:49:10 UTC
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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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/RHSA-2020:5633