Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
1
-
SDK22: AltN/P, FLE/rfc verif., SDK28: JSONSM, SparkT, Trainin, SDK30: cepnet, ES6, txns, SDK44: Build/CI & Analy. Ad. C, SDK40: Coll. Plumb./SDK3 Refac, SDK42: Analytics Additional
Description
Verify that the sdk works properly and handles any special hostname logging requirements with support for libcouchbase's alternate name and port support. See also CBD-2345
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Epic Link | CBD-2345 [ 80497 ] |
Rank | Ranked higher |
Status | New [ 10003 ] | Open [ 1 ] |
Fix Version/s | 2.4.1 [ 15210 ] |
Description | Verify that the sdk works properly and handles any special hostname logging requirements with support for libcouchbase's alternate name and port support. See also CBD-2345 |
Verify that the sdk works properly and handles any special hostname logging requirements with support for libcouchbase's alternate name and port support. See also CBD-2345
Validation In order to perform validation, an SDK engineer can use the following steps to launch a QE docker cluster with alternate names configured. The SDK should then confirm that they are able to connect to the cluster. * git pull master of [github.com/couchbaselabs/sdkqe-resource|http://github.com/couchbaselabs/sdkqe-resource] * docker pull sdk-s435.sc.couchbase.com/cblauncher:latest * run sdkqe-resource/utils/launcher/cbp.sh * the cluster will then start up and configure itself, including alternate names/ports * if you run sdkqe-resource/utils/dport, you should see a list of ports for access the UI h4. Testing Tests to confirm that the SDK correctly connects to a cluster with alternate names configured. These tests should include both a case where the application resides inside the container network (but the cluster still has external hostname/ports configured), as well as a case where the application resides outside of the container network. |
Description |
Verify that the sdk works properly and handles any special hostname logging requirements with support for libcouchbase's alternate name and port support. See also CBD-2345
Validation In order to perform validation, an SDK engineer can use the following steps to launch a QE docker cluster with alternate names configured. The SDK should then confirm that they are able to connect to the cluster. * git pull master of [github.com/couchbaselabs/sdkqe-resource|http://github.com/couchbaselabs/sdkqe-resource] * docker pull sdk-s435.sc.couchbase.com/cblauncher:latest * run sdkqe-resource/utils/launcher/cbp.sh * the cluster will then start up and configure itself, including alternate names/ports * if you run sdkqe-resource/utils/dport, you should see a list of ports for access the UI h4. Testing Tests to confirm that the SDK correctly connects to a cluster with alternate names configured. These tests should include both a case where the application resides inside the container network (but the cluster still has external hostname/ports configured), as well as a case where the application resides outside of the container network. |
Verify that the sdk works properly and handles any special hostname logging requirements with support for libcouchbase's alternate name and port support. See also CBD-2345
|
Fix Version/s | 2.4.1 [ 15217 ] | |
Fix Version/s | 2.4.0 [ 15210 ] |
Sprint | SDK22: AltN/P, FLE/rfc verif. [ 593 ] | SDK22: AltN/P, FLE/rfc verif., SDK28: JSONSM, SparkT, Trainin [ 593, 610 ] |
Sprint | SDK22: AltN/P, FLE/rfc verif., SDK28: JSONSM, SparkT, Trainin [ 593, 610 ] | SDK22: AltN/P, FLE/rfc verif., SDK28: JSONSM, SparkT, Trainin, SDK30: cepnet, txns, ES6 [ 593, 610, 611 ] |
Fix Version/s | 2.4.2 [ 15314 ] | |
Fix Version/s | 2.4.1 [ 15217 ] |
Fix Version/s | 2.4.3 [ 15415 ] | |
Fix Version/s | 2.4.2 [ 15314 ] |
Fix Version/s | 2.4.4 [ 15432 ] | |
Fix Version/s | 2.4.3 [ 15415 ] |
Fix Version/s | 2.4.3 [ 15415 ] | |
Fix Version/s | 2.4.4 [ 15432 ] |
Fix Version/s | 2.4.4 [ 15432 ] | |
Fix Version/s | 2.4.3 [ 15415 ] |
Sprint | SDK22: AltN/P, FLE/rfc verif., SDK28: JSONSM, SparkT, Trainin, SDK30: cepnet, ES6, txns [ 593, 610, 611 ] | SDK22: AltN/P, FLE/rfc verif., SDK28: JSONSM, SparkT, Trainin, SDK30: cepnet, ES6, txns, SDK40: Coll. Plumb./SDK3 Refac [ 593, 610, 611, 661 ] |
Rank | Ranked lower |
Sprint | SDK22: AltN/P, FLE/rfc verif., SDK28: JSONSM, SparkT, Trainin, SDK30: cepnet, ES6, txns, SDK40: Coll. Plumb./SDK3 Refac [ 593, 610, 611, 661 ] | SDK22: AltN/P, FLE/rfc verif., SDK28: JSONSM, SparkT, Trainin, SDK30: cepnet, ES6, txns, SDK40: Coll. Plumb./SDK3 Refac, SDK42: Analytics Additional [ 593, 610, 611, 661, 669 ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | Open [ 1 ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Actual Start | 2018-10-24 15:39 (issue has been started) |
Sprint | SDK22: AltN/P, FLE/rfc verif., SDK28: JSONSM, SparkT, Trainin, SDK30: cepnet, ES6, txns, SDK40: Coll. Plumb./SDK3 Refac, SDK42: Analytics Additional [ 593, 610, 611, 661, 669 ] | SDK22: AltN/P, FLE/rfc verif., SDK28: JSONSM, SparkT, Trainin, SDK30: cepnet, ES6, txns, SDK44: Build/CI & Analy. Ad. C, SDK40: Coll. Plumb./SDK3 Refac, SDK42: Analytics Additional [ 593, 610, 611, 641, 661, 669 ] |
Planned End | 2018-10-30 06:00 (started sprint) | |
Planned Start | 2018-10-30 06:00 (started sprint) |
Resolution | Fixed [ 1 ] | |
Status | In Progress [ 3 ] | Resolved [ 5 ] |
Actual End | 2018-11-05 11:19 (issue has been resolved) |
Story Points | 1 |
From inside the Docker container:
ok
test_default (couchbase.tests.cases.connection_t.AlternateNamesTest) ... ok
test_external (couchbase.tests.cases.connection_t.AlternateNamesTest) ... ok
From outside the container:
ERROR test_default (couchbase.tests.cases.connection_t.AlternateNamesTest) ... ERROR
test_external (couchbase.tests.cases.connection_t.AlternateNamesTest) ... ok