Details
Description
There are issues that can arise from non-default as well as non-homogenous external address configuration. When an external address is used for bootstrapping, all communication with the target cluster should be via external addresses. Any nodes that do not expose the mgmt[SSL] port [1] should be discounted as cluster nodes. Any KV nodes which not expose the kv[SSL] port [1] should be discounted as KV nodes.
[1] - the SSL ports are used when encryption mode is FULL, otherwise the non SSL ports are used.
The absence of any viable KV nodes at bootstrap time should result in a 400.
Attachments
Issue Links
- relates to
-
MB-40400 [CX] Remote link with alternate address fails w/ internal error if kv[SSL] and mgmt[SSL] ports are not mapped
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description |
There are issues that can arise from non-default as well as non-homogenous external address configuration. When an external address is used for bootstrapping, all communication with the target cluster should be via external addresses. Any nodes that do not expose the mgmt[SSL]* port should be discounted as cluster nodes. Any KV nodes which not expose the kv[SSL]* port should be discounted as KV nodes.
* - the SSL ports are used when encryption mode is FULL, otherwise the non SSL ports are used. The absence of any viable KV nodes at bootstrap time should result in a 400. |
There are issues that can arise from non-default as well as non-homogenous external address configuration. When an external address is used for bootstrapping, all communication with the target cluster should be via external addresses. Any nodes that do not expose the mgmt[SSL]** port should be discounted as cluster nodes. Any KV nodes which not expose the kv[SSL]** port should be discounted as KV nodes.
** the SSL ports are used when encryption mode is FULL, otherwise the non SSL ports are used. The absence of any viable KV nodes at bootstrap time should result in a 400. |
| Description |
There are issues that can arise from non-default as well as non-homogenous external address configuration. When an external address is used for bootstrapping, all communication with the target cluster should be via external addresses. Any nodes that do not expose the mgmt[SSL]** port should be discounted as cluster nodes. Any KV nodes which not expose the kv[SSL]** port should be discounted as KV nodes.
** the SSL ports are used when encryption mode is FULL, otherwise the non SSL ports are used. The absence of any viable KV nodes at bootstrap time should result in a 400. |
There are issues that can arise from non-default as well as non-homogenous external address configuration. When an external address is used for bootstrapping, all communication with the target cluster should be via external addresses. Any nodes that do not expose the mgmt[SSL] port [1] should be discounted as cluster nodes. Any KV nodes which not expose the kv[SSL] port [1] should be discounted as KV nodes.
[1] - the SSL ports are used when encryption mode is FULL, otherwise the non SSL ports are used. The absence of any viable KV nodes at bootstrap time should result in a 400. |
| Labels | releasenote |
| Sprint | CX Sprint 208 [ 1156 ] |
| Rank | Ranked higher |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Sprint | CX Sprint 208 [ 1156 ] | CX Sprint 208, CX Sprint 209 [ 1156, 1167 ] |
| Labels | releasenote | releasenote triaged |
| Fix Version/s | 6.6.1 [ 17002 ] | |
| Fix Version/s | 6.6.0 [ 16787 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
| Labels | releasenote triaged | releasenote request-dev-verify triaged |
| Labels | releasenote request-dev-verify triaged | request-dev-verify triaged |
| Comment |
[ Summary: *Known Issue* customer description TBD
_Workaround_: when using external addresses, ensure ALL couchbase nodes have mgmt[SSL] port exposed, and ensure ALL kv nodes have kv[SSL] port exposed. ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |