[chef] Re: 11 to 12.0.8-1 upgrade failure

["Stephen Delano" < >]

If you’re upgrading from Open Source Chef Server 11 (which it looks like you are), you can just uninstall the chef-server-core package and all of your data in /opt/chef-server and /var/opt/chef-server will still be there. Chef Server 12 is installed into /opt/opscode and /var/opt/opscode, as it’s a direct descendant of the previous Enterprise Chef package.

You’ll just need to re-symlink /usr/bin/chef-server-ctl to the binaries that are installed in /opt/chef-server/bin.

Hope that helps!

The next step is to get the upgrade working for you.

—
Stephen Delano - Engineering Lead, Chef

On Mon, Apr 27, 2015 at 11:02 AM, Jeff Blaine < " target="_blank"> > wrote:

Our upgrade from 11.1.3-1 to 12.0.8-1 has failed.

What now (below)?

Obvious answer is that it is time to revert to 11, our last PostgreSQL
dump and restore our saved /var/opt/chef-server from just before the
upgrade?

Is that the recommended course of action?

opt:rcf-cm-master# /opt/opscode/bin/chef-server-ctl upgrade
Upgrading with options #<OpenStruct skip_confirmation=false,
chef11_server_url="https://localhost",
chef12_server_url="https://localhost", upload_threads=10,
chef11_admin_client_name="admin",
chef11_admin_client_key="/etc/chef-server/admin.pem">
Open source Chef 11 server detected.
Would you like to upgrade? [yN]
y
Upgrading the open source Chef 11 server.
Chef 12 short organization name? r701
Chef 12 full organization name? r701
Creating /tmp/chef11-server-data20150427-29002-8br4r0 as the location to
save the open source Chef 11 server data
Ensuring Chef 12 server is stopped
Ensuring the open source Chef 11 server is started
ok: run: bookshelf: (pid 29022) 1s
ok: run: chef-expander: (pid 29067) 0s
ok: run: chef-server-webui: (pid 29072) 0s
ok: run: chef-solr: (pid 29093) 1s
ok: run: erchef: (pid 29142) 0s
ok: run: nginx: (pid 29160) 1s
ok: run: postgresql: (pid 29186) 0s
ok: run: rabbitmq: (pid 29195) 1s
Preparing knife to download data from the open source Chef 11 server
Writing knife config to /tmp/knife-config.rb for use in downloading open
source Chef 11 server data
Downloading data from the open source Chef 11 server
Running knife download
Created /clients
Created /cookbooks
Created /data_bags
Created /environments
Created /nodes
Created /roles
Created /users
Created /cookbooks/TEMP-rcf-gitlab-loadtest-0.1.0
...
Pulling open source Chef 11 database credentials
Finished downloading data from the open source Chef 11 server
Ensuring open source Chef 11 server is stopped
ok: down: bookshelf: 0s, normally up
ok: down: chef-expander: 0s, normally up
ok: down: chef-server-webui: 1s, normally up
ok: down: chef-solr: 0s, normally up
ok: down: erchef: 0s, normally up
ok: down: nginx: 1s, normally up
ok: down: postgresql: 0s, normally up
ok: down: rabbitmq: 1s, normally up
Open source Chef 11 server data downloaded to
/tmp/chef11-server-data20150427-29002-8br4r0
Created /tmp/chef12-server-data20150427-29002-15yrbkq as the location to
save the tranformed data
Transforming open source Chef 11 server data for upload to Chef 12 server
Data transformed and saved to /tmp/chef12-server-data20150427-29002-15yrbkq
Applying default_orgname with orgname r701.
Configuring the Chef 12 server for use
Starting Chef Client, version 12.0.3
resolving cookbooks for run list: ["private-chef::default"]
Synchronizing Cookbooks:
- private-chef
- enterprise
- apt
- yum
- runit
- build-essential
- yum-epel
Compiling Cookbooks...
Recipe: private-chef::default
* directory[/etc/opscode] action create (up to date)
* directory[/etc/opscode/logrotate.d] action create
- create new directory /etc/opscode/logrotate.d
- change mode from '' to '0755'
- change owner from '' to 'root'
- change group from '' to 'root'
...
Running handlers:
Running handlers complete
Chef Client finished, 456/473 resources updated in 157.043110691 seconds
opscode Reconfigured!
Ensuring Chef 12 server components are started
ok: run: bookshelf: (pid 2138) 8s
ok: run: nginx: (pid 2445) 4s
ok: run: oc_bifrost: (pid 1722) 14s
ok: run: oc_id: (pid 1785) 13s
ok: run: opscode-chef-mover: (pid 2488) 1s
ok: run: opscode-erchef: (pid 2320) 6s
ok: run: opscode-expander: (pid 2001) 11s
ok: run: opscode-expander-reindexer: (pid 2071) 10s
ok: run: opscode-solr4: (pid 1902) 12s
ok: run: postgresql: (pid 1699) 16s
ok: run: rabbitmq: (pid 31075) 122s
ok: run: redis_lb: (pid 1613) 24s
Chef 12 server started
Writing knife-ec-backup config to /tmp/knife-ec-backup-config.rb
Uploading transformed open source Chef 11 server data to Chef 12 server
Restoring users
Updating user record for jblaine
Updating user record for admin
...
Restoring organization[r701]
Restoring org admin data
Restoring the rest of the org
Created /clients/AB.OUR.ORG.json
...
Created /clients/zaz.json
...
Created /cookbooks/TEMP-rcf-gitlab-loadtest-0.1.0
Created /cookbooks/application_python-3.0.0
Created /cookbooks/application-3.0.0
Created /cookbooks/application_ruby-2.1.4
Created /cookbooks/apt-2.0.0
Created /cookbooks/apt-2.6.1
Created /cookbooks/bash-CVE-2014-6271-0.1.1
Created /cookbooks/auditd-0.1.3
...
Created /cookbooks/yum-mysql-community-0.1.12
Created /cookbooks/yum-mysql-community-0.1.8
Created /cookbooks/yum-mysql-community-0.1.13
ERROR: Chef::Exceptions::MetadataNotValid: Cookbook loaded at path(s)
[/tmp/d20150427-2865-1oc96tk/chef_handler] has invalid metadata: The
`name' attribute is required in cookbook metadata
Failed uploading transformed data to the Chef 12 server