Details
-
Bug
-
Resolution: Fixed
-
Major
-
1.6.4
-
None
-
None
-
1
Description
When connecting to a cluster using a non default port and the couchbase:// scheme we can trigger a panic when trying to use `cluster.Manager(username,password).Internal().GetNodesMetadata()`. This is triggering because we aren't pulling the http addresses from the agent and instead pull them from the supplied agentconfig (so no http addresses...). We also have no guards in place to prevent a nil pointer if there are no http addresses to use.
Attachments
Issue Links
- blocks
-
CBG-727 Panic when connecting to non-standard memcached port using couchbase(s):// scheme
- Closed
-
CBG-728 2.7.1 Backport CBG-727 - Panic when connecting to non-standard memcached port using couchbase(s):// scheme
- Closed
- relates to
-
GOCBC-821 Unable to use cluster.Manager without opening existing bucket first
- Closed