You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
F1203 13:59:18.599912 26267 controller.go:87] Unable to perform initial service nodePort check: unable to persist the updated port allocations: servicenodeportallocation "" cannot be updated: another caller has already initialized the resource
F1203 13:59:18.599912 26267 controller.go:87] Unable to perform
initial service nodePort check: unable to persist the updated port
allocations: servicenodeportallocation "" cannot be updated: another
caller has already initialized the resource
—
Reply to this email directly or view it on GitHub #5679 (comment).
This could happen when the create against etcd succeeds, but the etcd server responds back with a failure, the next (automatic) attempt fails because the allocation has already created the entry in etcd.
https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin/6790/console
E1103 19:15:39.322456 24879 serviceaccounts_controller.go:218] serviceaccounts "default" already exists
E1103 19:15:39.322784 24879 create_dockercfg_secrets.go:109] secrets "build-controller-token-6mk35" already exists
E1103 19:15:39.325543 24879 tokens_controller.go:156] secrets "build-controller-token-3c31q" already exists
F1103 19:15:39.327992 24879 run_components.go:390] Unable to initialize namespaces: unable to persist the updated namespace UID allocations: uidallocation "" cannot be updated: another caller has already initialized the resource
The text was updated successfully, but these errors were encountered: