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
{{ message }}
Repository navigation
Unable to remove LifecycleRule from GCS Resources again #595
If this issue is time-sensitive, I have submitted a corresponding issue with GCP support.
Bug Description
Per #554 we have been setting lifecycleRule to an empty list to remove lifecycle rules (and actually on all buckets with no lifecycle policy defined), which worked on config connector version 1.60.0. However, we recently noticed (on config connector version 1.69.0) that config connector fails with that configuration with "StorageBucket: cannot interpret non-list as list". In #554 it looks like kishorv06 had the same issue on config connector version 1.63.0
Additional Diagnostic Information
Kubernetes Cluster Version
Client Version: 1.20.8-dispatcher
Server Version: 1.20.10-gke.1600
Config Connector Version
1.69.0
Config Connector Mode
namespaced
Log Output
StorageBucket: cannot interpret non-list as list
Steps to Reproduce
Steps to reproduce the issue
Create a storgebucket resource with a lifecycleRule set to an empty list: []
@erik-carlson thanks for bringing this issue up. We missed the latest comment on that other issue that mentioned this problem.
Yes I can confirm that I am able to reproduce the same error. It seems the issue started in KCC v1.62.0. Let me take some time to further investigate and see what happened.
We've managed to narrow down the problem to a particular commit. It seems the problem was introduced due to an upgrade to one our dependencies, so it might take some time to understand what's going on. That's what we have so far -- we'll post updates accordingly.
Activity
jcanseco commentedon Jan 20, 2022
@erik-carlson thanks for bringing this issue up. We missed the latest comment on that other issue that mentioned this problem.
Yes I can confirm that I am able to reproduce the same error. It seems the issue started in KCC v1.62.0. Let me take some time to further investigate and see what happened.
jcanseco commentedon Jan 24, 2022
We've managed to narrow down the problem to a particular commit. It seems the problem was introduced due to an upgrade to one our dependencies, so it might take some time to understand what's going on. That's what we have so far -- we'll post updates accordingly.
jcanseco commentedon Apr 7, 2022
Hi folks, apologies for long delay. We've root-caused the issue and will put out a fix soon (next 1-2 releases).
maqiuyujoyce commentedon Apr 13, 2022
The fix is released in v1.81.0.