Description of problem: When I do a replace of bc which has existing builds, e.g. oc replace -f java8-buildconfig.yaml The next time a build is triggered or started it complains that build '1' already exists. I have to click "Start Build" until the build number increments to the next free number. This is crazy slow when lots of builds. Please can you have OS check for build when object is replaced and select the next available one - not start back at 1? Version-Release number of selected component (if applicable): 3.2 How reproducible: - execute few builds - do "oc replace" for build congif - execute build again Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This should be fixed with a separate status resource for build configs.
Reassigning to you Ben since you may have fixed it already.
This was fixed here: https://github.com/openshift/origin/pull/9568
and it's not something i think we'd backport, so the fix will be in 3.3.
oc v3.3.0.6 kubernetes v1.3.0+57fb9ac When replace bc lastVersion to an older version than existing builds, the cli will prompt successfully. But lastVersion will not be changed.And could trigger new builds with available build numbers. Move this bug as verified.
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-2016:1933