Howdy Chefs!
I thought you might want to know that we've released Chef 0.10.4 with
an awesome number of fixes.
Thanks for being part of the community!
--
Bryan McLellan | opscode | senior systems administrator
(c) 206.607.7108 | (t) @btmspox | (b) http://blog.loftninjas.org
On Fri, Aug 12, 2011 at 12:53 AM, Bryan McLellan btm@opscode.com wrote:
Howdy Chefs!
I thought you might want to know that we've released Chef 0.10.4 with
an awesome number of fixes.Chef 0.10.4 Released - Chef Blog | Chef
Thanks for being part of the community!
Congrats guys!
Matthew, many thanks. You rock.
BWT, I've seen the new 0.10.5 dev version is already in place. Do you
guys plan to name pre versions (RC, Beta, ...) something like
0.10.5.9X? That will be of great help to the packagers out there. RPM
is not clever enough to upgrade a 0.10.4.rc.X to a 0.10.4 unless you
use epoc versions or include the pre version in the release string...
--
Bryan McLellan | opscode | senior systems administrator
(c) 206.607.7108 | (t) @btmspox | (b) http://blog.loftninjas.org
On Aug 12, 2011 1:26 AM, "Sergio Rubio" rubiojr@frameos.org wrote:
BWT, I've seen the new 0.10.5 dev version is already in place. Do you
guys plan to name pre versions (RC, Beta, ...) something like
0.10.5.9X?
The versioning has always been modeled after the Linux kernel where even
numbers are stable point releases and odd numbers are development versions.
We haven't always remembered to do so after a release. However we are
working on building better process into releases.
The 'rc' in the version has to do with rubygems treating releases with alpha
characters as pre-releases.
On Fri, Aug 12, 2011 at 10:35 AM, Bryan McLellan btm@loftninjas.org wrote:
On Aug 12, 2011 1:26 AM, "Sergio Rubio" rubiojr@frameos.org wrote:
BWT, I've seen the new 0.10.5 dev version is already in place. Do you
guys plan to name pre versions (RC, Beta, ...) something like
0.10.5.9X?The versioning has always been modeled after the Linux kernel where even
numbers are stable point releases and odd numbers are development versions.
We haven't always remembered to do so after a release. However we are
working on building better process into releases.The 'rc' in the version has to do with rubygems treating releases with alpha
characters as pre-releases.
Thanks Bryan, great to know.
May I assume that the RC versioning scheme is going to continue the
way it is right now?
BTW, there are Opscode Chef 0.10.4 RPM packages now available in RBEL.
Install/upgrade instructions here:
http://blog.frameos.org/2011/08/12/chef-0-10-4-now-available-in-rbel/
I'd like to thank all of you who patiently suffered the ruby
segfaulting nightmare and reported back with the issues.
Rgds.
I had installed chef-server via the debian/ubuntu method, by adding the opscode apt repository.
I just did an apt-get update / apt-get upgrade and it broke.
Is there a recommended way to upgrade from 0.10.2 to 0.10.4 when using the prescribed apt methods?
$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
linux-image-virtual linux-virtual
The following packages will be upgraded:
chef chef-expander chef-server chef-server-api chef-server-webui chef-solr dbus dbus-x11 libdbus-1-3 libfreetype6 libpng12-0 libsndfile1 libsoup-gnome2.4-1 libsoup2.4-1 update-manager-core
15 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Need to get 1,931 kB of archives.
After this operation, 745 kB disk space will be freed.
Do you want to continue [Y/n]? y
Get:1 http://apt.opscode.com/ natty-0.10/main chef-server-api all 0.10.4-1 [46.6 kB]
Get:2 http://apt.opscode.com/ natty-0.10/main chef-expander all 0.10.4-1 [19.0 kB]
Get:3 http://apt.opscode.com/ natty-0.10/main chef-solr all 0.10.4-1 [32.5 kB]
Get:4 http://apt.opscode.com/ natty-0.10/main chef-server-webui all 0.10.4-1 [186 kB]
Get:5 http://apt.opscode.com/ natty-0.10/main chef-server all 0.10.4-1 [3,050 B]
Get:6 http://apt.opscode.com/ natty-0.10/main chef all 0.10.4-1 [333 kB]
Get:7 Index of /ubuntu natty-updates/main libdbus-1-3 i386 1.4.6-1ubuntu6.1 [123 kB]
Get:8 Index of /ubuntu natty-updates/main libfreetype6 i386 2.4.4-1ubuntu2.1 [314 kB]
Get:9 Index of /ubuntu natty-updates/main libpng12-0 i386 1.2.44-1ubuntu3.1 [126 kB]
Get:10 Index of /ubuntu natty-updates/main update-manager-core i386 1:0.150.3 [165 kB]
Get:11 Index of /ubuntu natty-updates/main dbus i386 1.4.6-1ubuntu6.1 [207 kB]
Get:12 Index of /ubuntu natty-updates/main dbus-x11 i386 1.4.6-1ubuntu6.1 [29.7 kB]
Get:13 Index of /ubuntu natty-updates/main libsndfile1 i386 1.0.23-1ubuntu0.1 [165 kB]
Get:14 Index of /ubuntu natty-updates/main libsoup2.4-1 i386 2.34.0-0ubuntu1.1 [172 kB]
Get:15 Index of /ubuntu natty-updates/main libsoup-gnome2.4-1 i386 2.34.0-0ubuntu1.1 [8,592 B]
Fetched 1,931 kB in 0s (7,642 kB/s)
Preconfiguring packages ...
(Reading database ... 58368 files and directories currently installed.)
Preparing to replace libdbus-1-3 1.4.6-1ubuntu6 (using .../libdbus-1-3_1.4.6-1ubuntu6.1_i386.deb) ...
Unpacking replacement libdbus-1-3 ...
Preparing to replace libfreetype6 2.4.4-1ubuntu2 (using .../libfreetype6_2.4.4-1ubuntu2.1_i386.deb) ...
Unpacking replacement libfreetype6 ...
Preparing to replace libpng12-0 1.2.44-1ubuntu3 (using .../libpng12-0_1.2.44-1ubuntu3.1_i386.deb) ...
Unpacking replacement libpng12-0 ...
Preparing to replace update-manager-core 1:0.150.2 (using .../update-manager-core_1%3a0.150.3_i386.deb) ...
Unpacking replacement update-manager-core ...
Preparing to replace chef-server-api 0.10.2-2 (using .../chef-server-api_0.10.4-1_all.deb) ...
dpkg: dependency problems prevent configuration of chef-server-webui:
chef-server-webui depends on chef-server (>= 0.10.4); however:
Package chef-server is not configured yet.
dpkg: error processing chef-server-webui (--configure):
dependency problems - leaving unconfigured
Setting up dbus (1.4.6-1ubuntu6.1) ...
Setting up dbus-x11 (1.4.6-1ubuntu6.1) ...
Setting up libsndfile1 (1.0.23-1ubuntu0.1) ...
Setting up libsoup2.4-1 (2.34.0-0ubuntu1.1) ...
Setting up libsoup-gnome2.4-1 (2.34.0-0ubuntu1.1) ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
Errors were encountered while processing:
chef-solr
chef-server-api
chef-expander
chef-server
chef-server-webui
E: Sub-process /usr/bin/dpkg returned an error code (1)
On Aug 11, 2011, at 5:53 PM, Bryan McLellan wrote:
Howdy Chefs!
I thought you might want to know that we've released Chef 0.10.4 with
an awesome number of fixes.Chef 0.10.4 Released - Chef Blog | Chef
Thanks for being part of the community!
--
Bryan McLellan | opscode | senior systems administrator
(c) 206.607.7108 | (t) @btmspox | (b) http://blog.loftninjas.org
On Fri, Aug 12, 2011 at 9:47 AM, Aaron Abramson aabramson@wi-figuys.com wrote:
I just did an apt-get update / apt-get upgrade and it broke.
Is there a recommended way to upgrade from 0.10.2 to 0.10.4 when using the prescribed apt methods?
This should work.
Setting up chef-solr (0.10.4-1) ...
Creating user "chef" ...
Error: {user_already_exists,<<"chef">>}
dpkg: error processing chef-solr (--configure):
subprocess installed post-installation script returned error exit status 2
This is http://tickets.opscode.com/browse/CHEF-2296, which should have
been fixed. I tested an upgrade myself and it worked okay.
Can you please run:
rabbitmqctl list_users
and
rabbitmqctl list_users | grep -x "^chef" 1>/dev/null ; echo $?
And provide the output?
The workaround is deleting the chef user in rabbitmq
sudo rabbitmqctl delete_user chef
Then continue apt with 'sudo apt-get install -f'
That appeared to work... (this is a vanilla Alestic Natty image (ami-06ad526f) with just chef-server installed.
$ sudo rabbitmqctl list_users
Listing users ...
chef false
guest true
...done.
$ sudo rabbitmqctl list_users | grep -x "^chef" 1>/dev/null ; echo $?
1
$ sudo rabbitmqctl delete_user chef
Deleting user "chef" ...
...done.
$ sudo apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libjs-jquery-ui wwwconfig-common javascript-common
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
5 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up chef-solr (0.10.4-1) ...
Creating user "chef" ...
...done.
Setting permissions for user "chef" in vhost "/chef" ...
...done.
On Aug 12, 2011, at 12:30 PM, Bryan McLellan wrote:
On Fri, Aug 12, 2011 at 9:47 AM, Aaron Abramson aabramson@wi-figuys.com wrote:
I just did an apt-get update / apt-get upgrade and it broke.
Is there a recommended way to upgrade from 0.10.2 to 0.10.4 when using the prescribed apt methods?
This should work.
Setting up chef-solr (0.10.4-1) ...
Creating user "chef" ...
Error: {user_already_exists,<<"chef">>}
dpkg: error processing chef-solr (--configure):
subprocess installed post-installation script returned error exit status 2This is http://tickets.opscode.com/browse/CHEF-2296, which should have
been fixed. I tested an upgrade myself and it worked okay.Can you please run:
rabbitmqctl list_users
and
rabbitmqctl list_users | grep -x "^chef" 1>/dev/null ; echo $?And provide the output?
The workaround is deleting the chef user in rabbitmq
sudo rabbitmqctl delete_user chef
Then continue apt with 'sudo apt-get install -f'
On Thu, Aug 11, 2011 at 3:53 PM, Bryan McLellan btm@opscode.com wrote:
Howdy Chefs!
I thought you might want to know that we've released Chef 0.10.4 with
an awesome number of fixes.Chef 0.10.4 Released - Chef Blog | Chef
Thanks for being part of the community!
For anyone interested I've added a document covering the new features
of the yum provider in 0.10.4:
http://wiki.opscode.com/display/chef/Yum+Package+Resource
--
Matthew Kent | http://magoazul.com
On Tue, Aug 16, 2011 at 12:04 AM, Matthew Kent
mkent+chef-users@magoazul.com wrote:
On Thu, Aug 11, 2011 at 3:53 PM, Bryan McLellan btm@opscode.com
For anyone interested I've added a document covering the new features
of the yum provider in 0.10.4:
This will be of great help. Thanks Matthew!
--
Matthew Kent | http://magoazul.com