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

cbopctl: Applying the yaml with mismatch of services and volume mounts not giving valid error messages

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 1.1.0
    • operator

    Description

      Server config yaml,

        servers:
          - size: 1
            name: data_only
            services:
              - data      # No index service defined, but volMnt defined for index
              - analytics
            pod:
              volumeMounts:
                default: couchbase
                data: couchbase
                index: couchbase
                analytics:
                  - couchbase
                  - couchbase

      cbopctl output:

      couchbase-operator]$ ./build/bin/cbopctl apply -f couchbase-cluster.yaml
      validation failure list:
      spec.servers[0].services in body cannot be updated

      Expected to get error message similar to create command like,

      couchbase-operator]$ ./build/bin/cbopctl create -f couchbase-cluster.yaml validation failure list:
      index in spec.servers[0].services is required

       

      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 -

          It doesn't work like that, if there is a field immutability issue when you perform an update it will die before running the validation step, so working as designed.  In fact there is no way to aggregate them together as that stuff is 3rd party and not exported.   I'll have a look at this, but it may have to wait until 1.2.0

          simon.murray Simon Murray added a comment - It doesn't work like that, if there is a field immutability issue when you perform an update it will die before running the validation step, so working as designed.  In fact there is no way to aggregate them together as that stuff is 3rd party and not exported.   I'll have a look at this, but it may have to wait until 1.2.0
          simon.murray Simon Murray added a comment -

          After some play time, I'm fairly certain it's a better user experience to say "you can't change this" rather than "you cann't change this and heres a much larger list of bad things to confuse matters"

          simon.murray Simon Murray added a comment - After some play time, I'm fairly certain it's a better user experience to say "you can't change this" rather than "you cann't change this and heres a much larger list of bad things to confuse matters"

          People

            simon.murray Simon Murray
            ashwin.govindarajulu Ashwin Govindarajulu
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty