[Backport MB-49879 to 7.0.4] Alter Index failure when nodes have un encrypted ports in encryption mode all

Description

ALTER INDEX `travel-sample`.country_idx
WITH {"action": "replica_count", "num_replica": 2, "nodes": ["127.0.0.1:9001", "127.0.0.1:9002", "127.0.0.1:9003"]}

Will fail when encryption is enabled.

The issues was introduced where we started supporting the use of encrypted ports from the query. We were only using un encrypted port numbers always.
The design is to support

  • only un encrypted port numbers when encryption was disabled

  • both un-encrypted and encrypted port numbers when encryption was set to all

  • only encrypted port numbers when encryption was strict

But after the change only encrypted ports are working in encryption mode all which breaks backwards compatibility.

Components

Affects versions

Fix versions

Labels

Environment

None

Link to Log File, atop/blg, CBCollectInfo, Core dump

None

Release Notes Description

None

Activity

Pavan PB May 5, 2022 at 4:08 PM

Verified with 7.0.4-7273.

Tests performed:
Create index with 8091 and then use alter to change the port to 18091 (using replica_count keyword).
Create index with 18091 and then use alter index to change the port to 8091 (using replica_count keyword).

The detailed steps are listed over here - > https://couchbasecloud.atlassian.net/browse/MB-49879?focusedCommentId=842010&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel

CB robot May 3, 2022 at 5:19 AM

Build couchbase-server-7.0.4-7273 contains indexing commit cd8522a with commit message:
: [BP to 7.0.4 of MB 49879] Allow non secure ports in Alter Index in Encryption mode all

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Is this a Regression?

Unknown

Triage

Triaged

Story Points

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created May 2, 2022 at 7:37 AM
Updated May 5, 2022 at 4:08 PM
Resolved May 3, 2022 at 2:47 PM
Instabug