> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmk/frequently-asked-questions/nodelet-initiating-stop-chain-on-failure-due-to-third-party-webh.md).

# Nodelet Initiating Stop Chain on Failure due to Third Party Webhook

## Problem

* Nodelet phases getting failed due to a failure while reaching a third party webhook.

{% tabs %}
{% tab title="C" %}

```c
{"L":"ERROR","T":"2024-07-04T03:07:35.903+0700","C":"misc/uncordon_node.go:103","M":"failed to remove annotation UserNodeCordon from node : failed to update node with removed annotations : Internal error occurred: failed calling webhook \"nodes.capsule.clastix.io\": failed to call webhook: Post \"https://capsule-webhook-service.capsule-system.svc:443/nodes?timeout=30s\": dial tcp 10.13.24.239:443: connect: connection refused"}
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed Kubernetes - v5.0 and Higher

## Cause

* Platform9 is still investigating the nodelet behavior via [PMK-6529](https://platform9.atlassian.net/browse/PMK-6529)

## Resolution

* The current workaround is to restart the nodelet stack.

```c
$ /opt/pf9/nodelet/nodeletd phases stop --force
$ /opt/pf9/nodelet/nodeletd phases start --force
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://platform9.com/kb/pmk/frequently-asked-questions/nodelet-initiating-stop-chain-on-failure-due-to-third-party-webh.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.