test/cmd/triggers.sh:40: error: buildconfigs "ruby-hello-world" cannot be updated

[liggitt]

Flake seen in #8286
https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin/13773/console

FAILURE after 0.129s: test/cmd/triggers.sh:40: executing 'oc set triggers bc/ruby-hello-world --remove-all' expecting success and text 'updated': the command returned the wrong error code
There was no output from the command.
Standard error from the command:
error: buildconfigs "ruby-hello-world" cannot be updated: the object has been modified; please apply your changes to the latest version and try again

set triggers is already using patch...

[bparees]

guessing this means there was a build running and the running build updated the BC(eg to set an imageid or a lastVersion value) right while this set was happening.

[liggitt]

That command is already using patch, so it would have to conflict 5 times to fail. Do we expect to be updating that many times that rapidly?

[bparees]

i don't think so...

[bparees]

you're saying patch re-gets and retries the patch operation 5 times when it hits conflicts?

[liggitt]

Yes, server-side

[liggitt]

See https://github.com/kubernetes/kubernetes/blob/master/pkg/apiserver/resthandler.go#L551

[smarterclayton]

@liggitt did we fix this or change in any way?

[liggitt]

not that I know of

[bparees]

no one else has reported this since it was opened at the end of march, closing based on unfounded optimism that the problem has gone away.