Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Garbage collector deleted wrong resources #88097
Looking at the audit logs I can see a spike in the number of objects being deleted by the garbage collector during the upgrade.
My theory is that the garbage collector started looking at the child resources before their parents were cached, would this be possible?
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
The description in the issue you linked seems like the opposite of what I'm describing. In my case the children had valid owner references pointing to valid parents that were not marked for deletion both the parents and the children were namespaced and in the same namespace.