Description of problem: Should remove 'loading..' when browser non-existent image Version-Release number of selected component (if applicable): Always How reproducible: OCP v3.9.1 Steps to Reproduce: 1. Login in web console 2. browser non-existent image via URL: console/project/pro1/browse/images/non-existent-image 3.browser non-existent pod via URL: console/project/pro1/browse/pods/non-existent-pod Actual results: 2. Will Always have "loading.." though the error "The image stream details could not be loaded" returned 3. NO ‘loading..’ words Expected results: Should remove 'loading..' when browser non-existent image like pod page. Additional info: image tag page has the same issue.
Commits pushed to master at https://github.com/openshift/origin-web-console https://github.com/openshift/origin-web-console/commit/b256cc02ceaee87d836dcb9046a4d10b3bdaaab8 Bug 1550797 - Should remove 'loading..' when browser non-existent image https://github.com/openshift/origin-web-console/commit/e3f6278722fce4d866563d9f209016f58f00ab13 Merge pull request #2867 from jhadvig/BZ1550797 Automatic merge from submit-queue. Bug 1550797 - Should remove 'loading..' when browser non-existent image Also fixed case when imageStream tag is missing/non-existing. @spadgett PTAL
Fixing PR: https://github.com/openshift/origin-web-console/pull/2867
If the fix are not going to ship in 33431, we will coordinate to drop it from the advisory
Please also see comment https://bugzilla.redhat.com/show_bug.cgi?id=1558863#c6
The target release was incorrectly set. This should be removed from the advisory. smunilla - can you help?
Samuel, could you help remove this bug from advisory 33431?
Sorry fixed merged in 3.10 and could be tested, moving back to ON_QA
Checked this issue in OCP v3.10.0-0.22.0, the 'loading' will disappear if the images/images tag is not existent. Samuel, the bug is still in advisory, please drop it. Thx
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/RHBA-2018:1566