Confusing error when object with generateName already exists

[liggitt]

Spawned from #10008 (comment)

https://github.com/openshift/origin/blob/master/vendor/k8s.io/kubernetes/pkg/api/rest/create.go#L106 is converting an AlreadyExists error into a server timeout error if it has a generateName

// CheckGeneratedNameError checks whether an error that occurred creating a resource is due
// to generation being unable to pick a valid name.
func CheckGeneratedNameError(strategy RESTCreateStrategy, err error, obj runtime.Object) error {
    if !errors.IsAlreadyExists(err) {
        return err
    }

    objectMeta, kind, kerr := objectMetaAndKind(strategy, obj)
    if kerr != nil {
        return kerr
    }

    if len(objectMeta.GenerateName) == 0 {
        return err
    }

    return errors.NewServerTimeoutForKind(kind.GroupKind(), "POST", 0)
}

That means that this returns really confusing errors:

data='{"kind":"Secret","apiVersion":"v1","metadata":{"name":"foo","generateName":"foo"}}'
$ oc create -f - <<< "$data"
secret "foo" created
$ oc create -f - <<< "$data"
Error from server: error when creating "STDIN": The POST operation against Secret could not be completed at this time, please try again.

[liggitt]

added in kubernetes/kubernetes@1588970#diff-40dfd6c156589ac2a34a471855aafab6R70, needs fix upstream

[derekwaynecarr]

created upstream issue to follow: kubernetes/kubernetes#32220

[openshift-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.

/lifecycle stale

[0xmichalis]

Closing in favor of the upstream issue