Hi Mark,
Thanks for the response. We have chef server 11 and 12 installed on the same node, which is arguably not the best approach but so be it.
So versions:
Chef Server 11.1.1-1
Chef Server 12.0.5-1
Chef Client 11.16.4-1
We trimmed down the amount of data in chef significantly and am running another export again. I dare not say that it’s going well for fear of jinxing it, except that it’s been running for > 6 hours.
Thanks
mike
—
Michael Hart
Arctic Wolf Networks
226.388.4773
From: Mark Mzyk
Reply-To: " "> " Date: Thursday, March 5, 2015 at 11:25 To: " "> " Subject: [chef] Re: Chef Server 12 upgrade failure Hi Michael,
You're correct that it's using knife download. To give you more insight into the process, all the upgrade code is here: https://github.com/chef/opscode-omnibus/tree/master/files/private-chef-ctl-commands Look at the chef12_upgrade* files and the open_source_chef12_upgrade.rb file. Specifically, the knife download is run here: https://github.com/chef/opscode-omnibus/blob/master/files/private-chef-ctl-commands/open_source_chef12_upgrade.rb I don't know why it would fail during the upgrade but work for you locally. On the upgrade it is using the bundled in chef-client that is used to configure the chef server, so perhaps it is a difference in client version. You can, if you explore the upgrade code, replicate manually what the upgrade code is doing using your local chef-client and then you could proceed on with the other steps. Can you tell me what version of the chef-client you're using that works? I think I've seen this error crop up for others but I'm not sure what causes it. Also what versions are your Chef 11 server and Chef 12 server package? Thanks, Mark " type="cite"> |
Archive powered by MHonArc 2.6.16.