Description of problem: Volumes table disappears while scrolling on initial load Version-Release number of selected component (if applicable): * Chrome: Version 80.0.3987.149 (Official Build) (64-bit) * Firefox: 68.6.0esr (64-bit) OpenShift: 4.5.0-0.ci-2020-04-01-001409 How reproducible: Follow the steps shown in the video after doing the below steps to setup a new application. Steps to Reproduce: 1. Once you have the a 4.5.X cluster built doing the following steps. a. copy the kube config file to local file > ${HOME}/kubconfig > export KUBECONFIG=${HOME}/kubconfig b. add kube pass to local env > export KUBE_PASS=xxxxxx c. login > oc login -u kubeadmin -p ${KUBE_PASS} d. create a namespace > oc create namespace [any-name as long as its not a duplicate, I usually use my user id] > export NAMESPACE=[namespace given to above command] e. create a new application. ( You can use my test app) **** this takes time to build **** > oc --namespace ${NAME_SPACE} new-app quay.io/quarkus/ubi-quarkus-native-s2i:19.3.1-java8~https://github.com/ddonahue007/quarkus-customer-demo.git --name=customer-demo f. You can either view logs through the UI or use the below command to see the build process if you want. > oc --namespace ${NAME_SPACE} logs -f bc/customer-demo 2. Once the build has finished you can use the console UI and you should see the same thing as the video Actual results: Expected results: Not to disappear Additional info:
Created attachment 1675407 [details] video of what I am experiencing.
1. Create project and application per comment 1 $ oc new-app quay.io/quarkus/ubi-quarkus-native-s2i:19.3.1-java8~https://github.com/ddonahue007/quarkus-customer-demo.git --name=customer-demo $ oc get pods NAME READY STATUS RESTARTS AGE customer-demo-1-build 1/1 Running 0 5m29s 2. Wait build pod is running, view Pod details on console, scroll down and up, rows in Volume table do not disappear Verified on 4.5.0-0.nightly-2020-04-07-201442
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-2020:2409