chef-solr debian package fail to detect existing rabbitmq user

This has hit me with upgrading from chef-solr 0.10 to 0.10.2 on Ubuntu 11.04. Following the description, here's what I get from rabbitmqctl:

root@overmind:~# rabbitmqctl list_users 
Listing users ...
chef	false
guest	true
...done.
root@overmind:~# rabbitmqctl list_users | cat -A
Listing users ...$
chef^Ifalse$
guest^Itrue$
...done.$
root@overmind:~# rabbitmqctl status
Status of node rabbit@overmind ...
[{running_applications,[{rabbit,"RabbitMQ","2.3.1"},
                        {os_mon,"CPO  CXC 138 46","2.2.4"},
                        {sasl,"SASL  CXC 138 11","2.1.8"},
                        {mnesia,"MNESIA  CXC 138 12","4.4.12"},
                        {stdlib,"ERTS  CXC 138 10","1.16.4"},
                        {kernel,"ERTS  CXC 138 10","2.13.4"}]},
 {nodes,[{disc,[rabbit@overmind]}]},
 {running_nodes,[rabbit@overmind]}]
...done.
root@overmind:~# dpkg -l rabbitmq-server
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name           Version        Description
+++-==============-==============-============================================
ii  rabbitmq-serve 2.3.1-1ubuntu1 An AMQP server written in Erlang

Deleting rabbitmq user (rabbitmqct delete_user chef) allowed me to upgrade the package.

The output of 'rabbitmqctl list_users' appears to have changed for natty, although I'm not sure what RabbitMQ version changed.

From https://github.com/puppetlabs/puppetlabs-openstack/issues/21:

version 1.8.1 (default squeeze)
root@squeeze:~# rabbitmqctl list_users
Listing users ...
guest
zone4_rabbit
...done.

version 1.8.0 (default maverick)
root@maverick:~# rabbitmqctl list_users
Listing users ...
guest
zone4_test
...done.

version 2.3.1 (default natty)
root@natty:~# rabbitmqctl list_users
Listing users ...
zone4_test true
zone4noadmin false
...done.

package chef-solr=0.10.2-5 is up on apt.opscode.com

removed the '-x' and the grep pattern is now "^chef"

tested upgrade on lucid + natty okay.

Reported issue still exists, CHEF-2545

grep -n list_users /var/lib/dpkg/info/chef-solr.postinst
21: rabbitmqctl list_users | grep -x "^chef" 1>/dev/null

with 'true' or 'false' after tabs on those lines now, this grep command should catch both variations:

rabbitmqctl list_users | grep -x "^chef(\W*\w*)$"

rabbitmqctl list_users | grep -x "^chef\\(\W*\w*
)$"
Notice the backslashes before the parenthesis. The commenting system seemed to grab those out.

rabbitmqctl list_users | grep -x "^chef(\W*\w*)$" 1>/dev/null

Where is the git repo for the debian build files? I'd like to contribute, but I'd like to know where upstream is.

deb-src http://apt.opscode.com/ natty-0.10 main # this is where I'm pulling from... where is the debian/rules etc for it?

Sometimes in the rash of for loops to put the debs in all the repositories, I forget to add the latest src as well.

Source is kept in http://github.com/opscode/opscode-packages

Thanks!

Should probably be more specific as . 'grep -x "^chef"' will match 'chefworks', 'cheffies', and 'chefzilla'.

https://github.com/opscode/opscode-packages/commit/1434374e5b446bac2ebb2aa1dd4b174ab6569d48#commitcomment-558636

So hard to put that in the comment system.

https://github.com/opscode/opscode-packages/pull/3

This issue is still active upgrading from chef 0.10.4-1 to 0.10.6-1, using deb packages from the Opscode repository.
Oneiric: 3.0.0-13-virtual x86_64

 
Setting up chef (0.10.6-1) ...
Installing new version of config file /etc/init.d/chef-client ...
 * Starting chef-client  chef-client                                                                                                      [ OK ]
Setting up chef-solr (0.10.6-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
dpkg: dependency problems prevent configuration of chef-expander:
 chef-expander depends on chef-solr (>= 0.10.6); however:
  Package chef-solr is not configured yet.
dpkg: error processing chef-expander (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of chef-server-api:
 chef-server-api depends on chef-solr (>= 0.10.6); however:
  Package chef-solr is not configured yet.
dpkg: error processing chef-server-api (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of chef-server:
 chef-server depends on chef-server-api (>= 0.10.6); however:
  Package chef-server-api is not configured yet.
 chef-server depends on chef-solr (>= 0.10.6); however:
  Package chef-solr is not configured yet.
 chef-server depends on chef-expander (>= 0.10.6); however:
  Package chef-expander is not configured yet.
dpkg: error processing chef-server (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of chef-server-webui:
 chef-server-webui depends on chef-server (>= 0.10.6); however:
  Package chef-server is not configured yet.
dpkg: error processing chef-server-webui (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 chef-solr
 chef-expander
 chef-server-api
 chef-server
 chef-server-webui

E: Sub-process /usr/bin/dpkg returned an error code (1)

Resolved by changing line 21 of /var/lib/dpkg/info/chef-solr.postinst to:

rabbitmqctl list_users | grep -e "^chef" 1>/dev/null

from:

rabbitmqctl list_users | grep -x "^chef" 1>/dev/null

and re-running installation.

I would like to confirm Graham Stewart's error report, as well as his fix. Thanks, Graham!

I've merged Hippie Hackers fix, and it should be in 0.10.8-2.

I performed a fresh install on Ubuntu 11.04, purged chef-solr, and then reinstalled it and had no issue with detecting the existing rabbitmq user. Looks good, I'm not going to test every Ubuntu platform.

I still hit this upgrading to 0.10.10-1:

Setting up chef-solr (0.10.10-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

The problem is still on line 21 of /var/lib/dpkg/info/chef-solr.postinst:

rabbitmqctl list_users | grep -x "^chef(\W*\w*)$" 1>/dev/null

It doesn't match the current `rabbitmqctl list_users` output:

Listing users ...
guest [administrator]
chef [management]
...done.

Note that I'm running Ubuntu 12.04, which uses RabbitMQ 2.7.1.

I'd suggest a less restrictive regex as the fix, just matching an end-of-word boundary:

rabbitmqctl list_users | grep "^chef\>"

Or to ensure that indention doesn't break it down the road, use a start-of-word boundary instead of start-of-line:

rabbitmqctl list_users | grep "\<chef\>"

Still present in 10.14.2-1. Fix, please?!

diff /var/lib/dpkg/info/chef-solr.postinst /var/lib/dpkg/info/chef-solr.postinst.fixed
21c21
< rabbitmqctl list_users | grep -x "^chef(\W*\w*)$" 1>/dev/null
—
> rabbitmqctl list_users | grep -x "^chef\W*[\W*\w*]$" 1>/dev/null

https://github.com/opscode/opscode-packages/pull/8

Is there any reason to use '[\W*\w*]' as oppose to just '.*'?

Adding to the list of rabbitmqctl outputs I created earlier:

Ubuntu 12.10 Quantal
rabbitmq-server=2.8.4-1

Listing users ...
guest	[administrator]
foo	[]
chef	[]
...done.

Paul Mooring, "^chef.*$" would match "chef [rabbit_junk]" as well as "chefdom [rabbit_junk]" which would be a false positive, albeit rare.

Ubuntu 12.04.1 LTS
rabbitmq-server 2.7.1-0ubuntu4

Listing users ...
guest	[administrator]
chef	[management]
...done.

Merged to opscode-packages/10-stable