A couple of days ago I have upgraded from community-7.0.2 to community-7.1.0 and from enterprise-7.0.3 to enterprise-7.1.0 for both of these I have noticed the following problems:
1, The Documents tab does not work anymore even though there are multiple buckets each filled with scopes and collections. Newly created buckets, scopes and collections also do not appear here if there is already a pre-existing bucket on the cluster, but if I delete all of the buckets and then create a new one the Documents tabs works again.
3, I have also noticed that there were random duplicate indexes (With identical name and definition), although I could not validate if those were created after the upgraded.
Is there a way to solve this without deleting the buckets? Currently only the development Clusters were upgraded and deleting the buckets there is fine, but eventually we want to upgrade the production cluster as well where that is not the case.
The cluster are runing on kubernetes using the official Couchbase dockers and the upgrade was done by changing the image tag in the Helm Chart.
Hi @horvath-martin can you explain the upgrade process here from 7.0.3 → 7.1.0 enterprise? The best way for us to understand what’s happening would be for you to share your helm-overrides along output from the resource collection tool. And you mentioned having a pre-existing bucket, was this created and managed by operator?
Also note that operator does not manage indexes and so it’s possible that duplicate indexes is outside of the scope of operator.
@Kevin.Cherkauer I have check it out in multiple browsers with cache cleared and it does not change anything. I suspect the old buckets are the cause. On one of our clusters I deleted all the buckets and created a new one and everything worked fine after that.
@horvath-martin When logged into the UI, what roles does the user have? There may be some permissions issues in retrieving the metadata to list the buckets/scopes/collections. The permissions-checking code changed between 7.0.3 and 7.1.
Do you see any errors in the browser’s error console?
Our buckets’s name contain the ‘.’ character multiple times and it seems like the “this.rbac.cluster.bucket” payload contains a nested map with the keys being the bucket name splitted on the ‘.’ character.
I have also checked the “this.rbac.cluster.collection” and it contains the correct keys eg.: “x.y.z:.:.”.
Are ‘.’ in the bucket name not supported anymore or is this a bug?
Thank you @horvath-martin! I tried reproducing the problem, but did not know that your bucket names included ‘.’ characters. Since ‘.’ characters are allowed, this should be supported. I’m investigating how to get that working.