The newly released 3.4.7 seems to have a new connection error:
Could not initialize Couchbase cluster and/or [BUCKET_NAME] bucket: Bucket with name [BUCKET_NAME] does not exist or cannot be reached. Couchbase.Management.Buckets.BucketNotFoundException: Bucket with name [BUCKET_NAME] does not exist or cannot be reached.
- at Couchbase.Core.ClusterContext.GetOrCreateBucketLockedAsync(String name)*
3.4.6 does not have this issue.
Can you describe your environment? Windows/Linux, docker, kubernetes, etc?
Is that the exception that is exposed? I didn’t see that in the ticket.
It’s a secondary exception that occurs after the other exception due to the bootstrap failure. Sorry I should have included it in the original report.
Confirmed fixed in 3.4.8. Thanks guys!
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.