Uploaded image for project: 'Couchbase Kubernetes'
  1. Couchbase Kubernetes
  2. K8S-1532

Upgraded Version not Persisted

    XMLWordPrintable

Details

    • 1

    Description

      The new base version needs to go in the persistent cache once upgrade is complete, otherwise we will reload and display the old one.

      We need to add in a regression test to ensure the version is as we expect for a period after the upgrade.

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          simon.murray Simon Murray added a comment -

          Release Note for 2.0.x

          We should tell them that the status need not reflect reality.

          simon.murray Simon Murray added a comment - Release Note for 2.0.x We should tell them that the status need not reflect reality.

          RN Description as a known issue in 2.0.x:
          When upgrade from Couchbase Server 6.5.0 to 6.5.1 is performed by the Operator, the resulting deployment may show 6.5.0 as the version, though the individual nodes in the pods are in fact running version 6.5.1.

          RN Description as a fixed issue in 2.1:
          It was possible that an upgrade carried out by the Operator may still an old version in the deployment. Now, when upgrade is done, the correct version will be shown.

          ingenthr Matt Ingenthron added a comment - RN Description as a known issue in 2.0.x: When upgrade from Couchbase Server 6.5.0 to 6.5.1 is performed by the Operator, the resulting deployment may show 6.5.0 as the version, though the individual nodes in the pods are in fact running version 6.5.1. RN Description as a fixed issue in 2.1: It was possible that an upgrade carried out by the Operator may still an old version in the deployment. Now, when upgrade is done, the correct version will be shown.
          eric.schneider Eric Schneider (Inactive) added a comment - - edited

          Description for release notes:

          *Summary:* When using the Autonomous Operator to upgrade Couchbase Server from version 6.5.0 to 6.5.1, the resulting deployment may still show 6.5.0 as the version, even though the individual nodes in the pods are in fact running version 6.5.1.
          //Include the following statement in the description of this issue when it is moved to the fixed issues table in the 2.1 RN.
          //It was possible that when using the Autonomous Operator to upgrade Couchbase Server from version 6.5.0 to 6.5.1, the resulting deployment would still show 6.5.0 as the version, even though the individual nodes in the pods are in fact running version 6.5.1.//Now, when an upgrade of Couchbase Server completes, the correct upgraded version is shown.
          

          eric.schneider Eric Schneider (Inactive) added a comment - - edited Description for release notes: *Summary:* When using the Autonomous Operator to upgrade Couchbase Server from version 6.5.0 to 6.5.1, the resulting deployment may still show 6.5.0 as the version, even though the individual nodes in the pods are in fact running version 6.5.1. //Include the following statement in the description of this issue when it is moved to the fixed issues table in the 2.1 RN. //It was possible that when using the Autonomous Operator to upgrade Couchbase Server from version 6.5.0 to 6.5.1, the resulting deployment would still show 6.5.0 as the version, even though the individual nodes in the pods are in fact running version 6.5.1.//Now, when an upgrade of Couchbase Server completes, the correct upgraded version is shown.

          People

            simon.murray Simon Murray
            simon.murray Simon Murray
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty