cockroachdb / cockroachdb/helm-charts

User creation during provisioning step fails

Open
#509 6 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
105
Forks
152
Avg merge
4d 23h
Merged PRs (30d)
5

Description

When using the `init.provisioning.enabled: true` and attempting to create a user for the database, the init script always fails with an error message:
```
cluster-init ++ /cockroach/cockroach init --certs-dir=/cockroach-certs/ --cluster-name=dev --host=cockroachdb-0.cockroachdb:26257
cluster-init E250502 01:51:04.786205 29 2@rpc/peer.go:679 [rnode=?,raddr=cockroachdb-0.cockroachdb:26257,class=system,rpc] 1 failed connection attempt (last connected 0s ago): grpc:
cluster-init ERROR: empty passwords are not permitted
cluster-init Failed running "sql"
cluster-init Provisioning completed successfully
```

My helm values config contains the following:
```
init:
provisioning:
enabled: true
users:
- name: devuser
password: devpassword123
options:
- LOGIN
databases:
- name: crdb
owners:
- devuser

```

I'm not really sure why it says `empty passwords` but I can't find any explanation for what is expected in the password field.

Jira issue: HELM-54

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the Helm values under init.provisioning and the chart's provisioning init script, then inspect the rendered manifest to see how the users.password value is passed to the database command. Reproduce with the supplied devuser configuration; done means the user and database are created without the empty-password error and the provisioning step reports success.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm
Domain
devops
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.