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

not able to set conflict resolution to timestamp on a new bucket

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 0.7.0
    • None
    • operator

    Description

      1. Create a couchbase cluser with config example/couchbase-cluster.yaml
      2. default bucket created as per the config with resolution seqno (logs1)
      3. Apply a new config with no buckets (arun-cluster.yaml)
      4. ensure bucket default is deleted from cluster (logs2)
      5. Apply a new config with bucket arun-bucket with conflict resolution timstamp (arun-cluster2.yaml)
      6. bucket arun-bucket created but conflict resolution still says seqno (logs3)

      attaching screenshots

      Attachments

        1. arun-cluster.yaml
          0.6 kB
        2. arun-cluster2.yaml
          0.9 kB
        3. logs1.rtf
          4 kB
        4. logs2.rtf
          4 kB
        5. logs3.rtf
          4 kB
        6. Screen Shot 2018-01-16 at 12.23.01 PM.png
          Screen Shot 2018-01-16 at 12.23.01 PM.png
          84 kB
        7. Screen Shot 2018-01-16 at 12.25.58 PM.png
          Screen Shot 2018-01-16 at 12.25.58 PM.png
          31 kB
        8. Screen Shot 2018-01-16 at 12.27.22 PM.png
          Screen Shot 2018-01-16 at 12.27.22 PM.png
          107 kB
        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            arunkumar Arunkumar Senthilnathan (Inactive)
            arunkumar Arunkumar Senthilnathan (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty