Select a documentation version: <button class="button button-with-icon cloud-select-dropdown__button button-primary" aria-haspopup="true">18.4.0</button>

- [Current (18.4.0)](https://docs.cloud.google.com/alloydb/omni/redhat-orchestrator/current/docs/troubleshoot-cluster-creation.md.txt)
- [18.4.0](https://docs.cloud.google.com/alloydb/omni/redhat-orchestrator/18.4.0/docs/troubleshoot-cluster-creation.md.txt)
- [18.3.0](https://docs.cloud.google.com/alloydb/omni/redhat-orchestrator/18.3.0/docs/troubleshoot-cluster-creation.md.txt)

<br />

This page shows you how to resolve issues with AlloyDB Omni using the RPM orchestrator.

<br />

## Cluster creation errors

This section lists cluster creation errors that you might encounter and
explains how to resolve them.

### Installation fails because privilege escalation isn't enabled

The following issue occurs when the `ansible_user` variable in your installation
playbook specifies a non-root user and the play doesn't enable privilege
escalation:

```
This command has to be run under the root user.
```

This issue occurs because the `google.alloydbomni_orchestrator.install` role
installs packages with the `dnf` package manager, which requires root
privileges.

To resolve this issue, do the following:

1. In your playbook, add `become: true` at the play level, as shown in [Install AlloyDB Omni components using Ansible](https://docs.cloud.google.com/alloydb/omni/redhat-orchestrator/current/docs/install-components.md.txt#install-using-ansible).
2. Verify that the user in the `ansible_user` variable can run `sudo` on every node in the inventory.
3. Run the playbook again:

   ```bash
   ansible-playbook -i deployment_spec.yaml install.yaml
   ```

To verify that the issue is resolved, check that the task
`Install SELinux python utilities` reports `ok` or `changed`, and that the play
recap shows `failed=0` for every host.

### Bootstrap fails because the data directory doesn't exist on database nodes

The following issue occurs when the bootstrap playbook times out on all database
nodes with the message
`Timeout when waiting for DB_NODE_1:5432`, and the Node
Manager log shows an error related to a missing data directory.

To identify the missing directory, do the following:

1. Use `journalctl` to check the Node Manager log:

   ```bash
   sudo journalctl -u alloydbomni_node_manager
   ```
2. Check the output for a message similar to the following:

   ```
   service "dbprocess": root data directory does not exist: PG_DATA_DIR
   ```

These messages include the following values:

- `DB_NODE_1`: the IP address or fully qualified domain name (FQDN) of a database node.
- `PG_DATA_DIR`: the host path to the directory where the database data is stored.

This issue occurs because `PG_DATA_DIR` doesn't exist on every
database node. The orchestrator expects the directory to exist before bootstrap.

To resolve this issue, do the following:

1. On every database node, create `PG_DATA_DIR` and mount the external volume to it. For more information, see [Create a cluster](https://docs.cloud.google.com/alloydb/omni/redhat-orchestrator/current/docs/create-cluster.md.txt#before-you-begin).
2. Configure the mount to persist across reboots.
3. Run the bootstrap playbook again.

To verify that the issue is resolved, run the following command:

```bash
alloydbctl get -d deployment_spec.yaml -t DBCluster -n CLUSTER_NAME -o yaml
```

Replace `CLUSTER_NAME` with the name of your database cluster.

The output shows the `DatabaseReady` condition with `status: "True"`.

### Bootstrap fails because `DBCluster` parameter values aren't quoted

The following issue occurs when the `parameters` section of your `DBCluster`
specification contains numeric values without quotation marks, and you run the
playbook that invokes the `google.alloydbomni_orchestrator.bootstrap` role:

```
invalid parameters in DBCluster resource specification: json: cannot unmarshal number into Go struct field AlInstanceSpec.primarySpec.InstanceSpec.parameters of type string
```

This issue occurs because each entry under the `parameters` field is a key-value
string pair, as described in
[DBCluster Custom Resource Definition](https://docs.cloud.google.com/alloydb/omni/redhat-orchestrator/current/docs/reference/dbcluster-spec.md.txt#primarySpec.parameters).

To resolve this issue, do the following:

1. Enclose every value under the `spec.primarySpec.parameters` field in quotation marks,
   as shown in
   [Prepare cluster specifications](https://docs.cloud.google.com/alloydb/omni/redhat-orchestrator/current/docs/create-cluster.md.txt#prepare-specifications):

   ```yaml
   DBCluster:
     spec:
       primarySpec:
         parameters:
           max_connections: "100"
           max_wal_size: "2GB"
   ```
2. Run the bootstrap playbook again.

To verify that the issue is resolved, run the following command:

```bash
alloydbctl get -d deployment_spec.yaml -t DBCluster -n CLUSTER_NAME -o yaml
```

Replace `CLUSTER_NAME` with the name of your database cluster.

The output shows the `DatabaseReady` condition with `status: "True"`.