Red Hat Bugzilla – Bug 1484563
You should not be able to modify metadata.generation in a DC
Last modified: 2017-11-28 17:07:41 EST
Description of problem: If the metadata.generation value is lower than the status.observedGeneration the DC is no longer modifiable. The master (or master-controllers) service will log an error that the DC cannot be updated because the "status.observedGeneration cannot be decremented". Version-Release number of selected component (if applicable): OCP 3.3.1 How reproducible: 100% Steps to Reproduce: 1. oc edit dc <test_app> 2. change the metadata.generation to a lower value (for example: 5->3) and save 3. oc scale dc <test_app> --replicas=<Different_number> Actual results: Pod scales up/down to match the specified replicas BUT an error message about updating the DC will appear in the master (or master-controllers) service logs and if you check `oc get dc <test_app>` it will reference the old replica number Expected results: metadata.generation is not changed therefore the scale and everything adjusts properly. Additional info: OpenShift is unable to make additional modifications to an application's DC (including scaling) if the DC's .spec.observedGeneration is greater than the .metadata.generation value. Neither of these fields are things that the user should have any reason to modify but the .metadata.generation can be modified.
It seems like in general, if we never expect observedGeneration to go down, ValidateObjectMetaUpdate in Kubernetes should probably prevent `Generation` from going down as well. I believe the error is specifically in regards to status updates -- spec-only updates seem to go through. However, incorrect status causes issues with things which depend on status for information, such as the HPA, which consumes `status.replicas` via the scale subresource.
Not merged with latest OCP v3.3.1.46.16
Confirmed with OCP v3.3.1.46.31, now can't update the generation. openshift v3.3.1.46.31 kubernetes v1.3.0+52492b4 etcd 2.3.0+git
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/RHSA-2017:3188