Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Ensure undeploy is always available

Description

It is seen in forums post that functions cannot be undeployed during bootstrap. Because undeploy is the escape hatch when system encounters unrecoverable errors, it should never be disabled.

Components

Affects versions

Fix versions

Labels

Environment

None

Link to Log File, atop/blg, CBCollectInfo, Core dump

None

Release Notes Description

None

Activity

Sriram Melkote May 23, 2018 at 12:35 PM

Hi , only internal use, this isn't a supported public API

Balakumaran Gopal May 15, 2018 at 6:02 AM

I tried as suggested.

1) Deleted metadata bucket while eventing is bootstrapping.
2) Ran the api POST /api/v1/functions/<name>/retry
{
"count" : <number>
}
3) After executing the REST API, the function state changed to deployed and I was able to undeploy and delete the function.

Balakumaran Gopal May 14, 2018 at 9:02 AM

Validated this on Enterprise Edition 5.5.0 build 2709 ‧ IPv4.

1) deployed a function
2) flush/delete metadata bucket
3) Undeploy/delete the function.

Undeploy/deleting the function works fine. Hence marking this bug closed.

CB robot May 10, 2018 at 12:38 PM

Build couchbase-server-6.0.0-1118 contains eventing commit df61dffc15262631e1d149e4007fb3fe4836a50a with commit message:
Ensure Undeploy is always available
https://github.com/couchbase/eventing/commit/df61dffc15262631e1d149e4007fb3fe4836a50a

CB robot May 10, 2018 at 9:34 AM

Build couchbase-server-5.5.0-2697 contains eventing commit df61dffc15262631e1d149e4007fb3fe4836a50a with commit message:
Ensure Undeploy is always available
https://github.com/couchbase/eventing/commit/df61dffc15262631e1d149e4007fb3fe4836a50a

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Is this a Regression?

Unknown

Triage

Untriaged

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created March 14, 2018 at 8:34 AM
Updated May 23, 2018 at 12:35 PM
Resolved May 7, 2018 at 9:47 AM
Instabug