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

Analyze 1.0.0-217 failures

    XMLWordPrintable

Details

    • Task
    • Resolution: Fixed
    • Major
    • 1.0.0
    • None
    • None
    • None

    Description

      Please analyze the failures listed in the weekly report for 1.0.0-217 (5.1.0) . It looks like there are some new events and some of the messages have changed. Those failure you can ignore for now. I would say go through them all and pick out 3 that look like bugs and not event or message related failures and open bugs. Don’t spend too much time on this as you need to focus on infrastructure changes, but lets open some bugs early so dev can start working on them.

      Attachments

        Issue Links

          depends on

          Bug - A problem which impairs or prevents the functions of the product. K8S-356 ResizeCluster call fails to add desired number of nodes to cluster during node failure case

          • Test Blocker - QE-related tests can't proceed
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. K8S-355 Testcase fails with panic issue during RetryOnErr call

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. K8S-357 WaitClusterStatusHealthy api call fails with wrong results

          • Major - Major loss of function.
          • Closed

          Activity

            People

              korrigan.clark Korrigan Clark (Inactive)
              korrigan.clark Korrigan Clark (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                PagerDuty