kcp-dev
Namespace is likely modified somewhere without a DeepCopy
From https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-kcp-dev-kcp-main-e2e-shared-periodic/1626703272859406336, got a concurrent map iterate + write when trying to deep copy a namespace (specifically, its annotations). It seems like we are probably modifying a namespace from an informer cache without having made a deep copy first.
This failure was in a private kcp server, which doesn't have the env propagated to enable the cache mutation detector. Need to fix that.
Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close
@kcp-ci-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopen. Mark the issue as fresh with/remove-lifecycle rotten./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.