Description of problem: In an OCP 3.7 latest environments, build numbers are non sequential. For instance, duing a series of builds, builds 1,2 are shown in the build history, build 3 is skipped, and builds 4,5 are shown. This seems very similar to the upstream issue below:
Version-Release number of selected component (if applicable):
Have not been able to reproduce this in house.
Steps to Reproduce:
Actual results: Builds 1,2,4,5,7 are shown in the build history.
Expected results: Builds 1-7 are all shown.
your issue says builds but your screenshot shows deployments...which one are you having issues with?
The end user is complaining about the screenshot. So this should probably be under deployments. Sorry for the confusion. I'll try to get the node logs showing these deployments as well. Not sure if they went to the same node or not yet.
ok, i've reassigned and fixed the bug title.
Seems that the sequence is broken after the previous deployment was cancelled. Can you verify using `oc get rc` if this is not just a web-console rendering issue?
Also I can't reproduce this on 3.9 or 3.10, so if this was a bug it is likely fixed in the recent version.