Description of problem: When changing the health check url probe it gives the status as updated : oc set probe dc/hello-world --readiness --get-url=<a href='http://:8080/'>http://:8080/</a> and then scale dc it starts but later fails to deploy the new replicas as below 12s 12s 1 {deployment-controller } Warning FailedUpdate Cannot update deployment syseng-validation/hello-world-1 status to Pending: replicationcontrollers "hello-world-1" cannot be updated: the object has been modified; please apply your changes to the latest version and try again 2) When initiating the scaling first and changing the health check probe later. It succeeds. Below error is seen : Events: FirstSeen LastSeen Count From SubobjectPath Type Reason Message --------- -------- ----- ---- ------------- -------- ------ ------- 12s 12s 1 {deploymentconfig-controller } Normal DeploymentCreated Created new deployment "hello-world-1" for version 1 12s 12s 1 {deployment-controller } Warning FailedUpdate Cannot update deployment syseng-validation/hello-world-1 status to Pending: replicationcontrollers "hello-world-1" cannot be updated: the object has been modified; please apply your changes to the latest version and try again Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: If it says the the healthcheck probe url is updated then it should have succeeded while it fails. Expected results: It should have succeeded without issue. Additional info:
This is not a regression but a known issue we have taken because of backwards-compatibility concerns. There is similar discussion in https://bugzilla.redhat.com/show_bug.cgi?id=1306720
Closing as duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1333129 *** This bug has been marked as a duplicate of bug 1333129 ***