> 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/pcd/self-hosted/unable-to-generate-support-bundle-from-non-primary-masters.md).

# Unable to Generate Support Bundle From Non-Primary Masters

## Problem

* Attempting to generate a support bundle from secondary/non-primary master/controller nodes in a Self-Hosted control plane fails.

{% tabs %}
{% tab title="airctl gen-support-bundle" %}

```bash
failed to create k8s context: failed to build config: stat /etc/nodelet/airctl-mgmt/certs/admin.kubeconfig: no such file or directory failed to Parse Cluster Config: error opening bootstrap config file
```

{% endtab %}
{% endtabs %}

* If the first master is down or unavailable, it is **not possible to generate support bundles** from secondary masters.

## Environment

* Self-Hosted Private Cloud Director Virtualization - v2025.4 and Higher
* airctl

## Cause

* `airctl` utility requires the bootstrap configuration file `/opt/pf9/airctl/conf/nodelet-bootstrap-config.yaml` to generate support bundles for controller/master nodes.
* This file exists **only on the primary/first master node**.
* Secondary masters do not have this file, making support bundle generation from them impossible.

## Diagnostics

1. Attempt to generate support bundle from a secondary master.

{% tabs %}
{% tab title="Secondary/Tertiary Master Node" %}

```bash
$ sudo airctl gen-support-bundle --host-ips <secondary_master_ip> --config <config_file> --verbose
```

{% endtab %}
{% endtabs %}

2. Verify bootstrap config presence:

{% tabs %}
{% tab title="Secondary/Tertiary Master Node" %}

```bash
$ ls -l /opt/pf9/airctl/conf/nodelet-bootstrap-config.yaml
```

{% endtab %}
{% endtabs %}

## Resolution

1. Identify the first/primary master node by reviewing the `airctl-config.yaml` file. It consists of hosts section and an ordered list of master IPs. The first entry in the list is considered as the primary master and vice-versa.
2. SSH into the **first/master node**.
3. Run support bundle generation using `airctl` from the first master:

{% tabs %}
{% tab title="Primary Master" %}

```bash
$ sudo airctl gen-support-bundle --host-ips <all_master_ips> --config <config_file> --verbose
```

{% endtab %}
{% endtabs %}

{% hint style="warning" %}
**Warning**

If the first master is unavailable, generating support bundles from other masters is not possible. Restoration of the first master or Platform9 Support assistance will be required.
{% endhint %}

## Additional Information

Platform9 has raised an internal JIRA to implement functionality allowing support bundle generation **from any master node**, regardless of whether it is the primary or secondary master. **PCD-4580** to track the filed bug.


---

# 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 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/pcd/self-hosted/unable-to-generate-support-bundle-from-non-primary-masters.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 `automate deployments from our CI pipeline` 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.