chef / chef/chef-server

Documentation for backup/restore is missing a few steps

Open
#476 2 comments 1 reaction 1 assignee View on GitHub

@lbakerchef is already working on this.

Since Jul 1, 2021.

Aspect: Documentation Status: Consider for next release Status: Good First Issue Triage: Confirmed
Dominant language
Erlang
Stars
303
Forks
211
Avg merge
1d 8h
Merged PRs (30d)
5

Description

The documentation for backup/restore at https://docs.chef.io/server_backup_restore.html is overall very good, but if you follow it verbatim, it will use the old SSL certificate for the old server's FQDN.

Before the chef-server-ctl reconfigure command, the following should be added:

Ideally, the server you restore to will have the same FQDN as the one you backed up. If this is not possible, perform the following additional steps:

edit /etc/opscode/chef-server.rb and /etc/opscode/chef-server-running.json to replace the old FQDN with the new one.

Delete the old SSL certificate, key and -ssl.conf file from /var/opt/opscode/nginx/ca . If you use a CA-issued certificate instead of a self-signed certificate, copy that certificate and key into the same directory.

On each client, update the /etc/chef/client.rb file to point to the new server.

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.