Upgrade of single node IPv6 cluster from 5.5.0 can lose all data

Description

If a single node (using loopback address ::1) cluster has been configured in IPv6 mode in 5.5.0 and an attempt is made to upgrade the cluster to later versions, then all data will be lost. This is because the cbupgrade script doesn't handle IPv6 loopback address correctly. The reason for this is that the script can't determine if the cluster has been operating in IPv6 mode as the static_config would've got overwritten as part of the upgrade.

Note that this problem will not be seen on a single node cluster where the node was configured with an FQDN. Since single node cluster configured in IPv6 mode using loopback address will not be a production cluster, we've decided not to fix this but to document the behavior.

Environment

None

Release Notes Description

None

Activity

Show:

Beth Favini September 19, 2023 at 7:02 PM

This ticket is being closed as part of the docs team’s effort to increase focus on relevant doc work. We are closing all open tickets that were created before January 2022. This bulk change will help us better manage a large historical backlog and identify high-priority issues. We’ve tagged all tickets closed as part of this effort with the label bulkclosed20230919. We encourage you to reopen this and any other ticket you think is still relevant.

Won't Fix
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Labels

Story Points

Components

Fix versions

Affects versions

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created June 27, 2019 at 7:22 PM
Updated September 19, 2023 at 7:02 PM
Resolved September 19, 2023 at 7:02 PM
Instabug