chef / chef/chef-server

ERROR: relation "keys" does not exist

Open
#2,484 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Aspect: Portability Triage: Try Reproducing
Dominant language
Erlang
Stars
303
Forks
211
Avg merge
1d 8h
Merged PRs (30d)
5

Description

fter run chef-server-ctl reconfigure I have this error, Any idea? * ruby_block[bootstrap-chef-server-data] action run ================================================================================
Error executing action run on resource 'ruby_block[bootstrap-chef-server-data]'
================================================================================ PG::UndefinedTable
------------------
ERROR: relation "keys" does not exist
LINE 1: INSERT INTO keys (id, key_name, public_key, key_version, cre...

chef-stacktrace.txt

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the attached chef-stacktrace.txt and tracing chef-server-ctl reconfigure to ruby_block[bootstrap-chef-server-data]. Reproduce the failure and determine why the bootstrap insert cannot find the keys relation; done means reconfigure completes without the PG::UndefinedTable error.

Written by the indexing model from the issue text.

Assessment

Tech stack
erlang, postgresql
Domain
backend, databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.