Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-36300

Undeployment hung when handler deployed with default log_level

    XMLWordPrintable

Details

    Description

      Build: 6.0.3-2893 last good build 6.0.3-2880

      ./testrunner -i vikas-nodes.ini -t eventing.eventing_settings.EventingSettings.test_default_log_level,nodes_init=4,services_init=kv-eventing-index-n1ql,dataset=default,groups=simple,reset_services=True,skip_cleanup=True

      We deploy handler without log_level in settings, then undeploy.
      No doc in metadata but undeployment hung for more then 30 min
       

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MB-36023 [BP MB-35996] - function deployment fails if imported/created in UI and deployed by couchbase-cli

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          For Gerrit Dashboard: MB-36300
          # Subject Branch Project Status CR V
          115837,1 MB-36300: Revert "MB-36023: Fix deployment through couchbase-cli" alice eventing Status: ABANDONED 0 0
          115840,3 MB-36300 Fix for panic in eventing producer alice eventing Status: MERGED +2 +1
          115956,2 MB-36300: Unlock eventing for 6.0.3 builds master manifest Status: MERGED +2 +1

          Activity

            People

              vikas.chaudhary Vikas Chaudhary
              vikas.chaudhary Vikas Chaudhary
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty