cannot access /etc/rabbitmq/rabbitmq.conf.d: No such file or directory upgrading from precise maas to trusty

[Diogo Matsubara]

Today I performed an upgrade from 1.4+bzr1693+dfsg-0ubuntu2.3~ctools0 to 1.5+bzr2204-0ubuntu1 and got this error from rabbit:

Considering dependency proxy for proxy_http:
Module proxy already enabled
Module proxy_http already enabled
Module expires already enabled
Module wsgi already enabled
 * Restarting message broker rabbitmq-server
   ...done.
ls: cannot access /etc/rabbitmq/rabbitmq.conf.d: No such file or directory
Error: {'EXIT',
           {terminated,
               [{io,nl,[<0.30.0>],[]},
                {lists,foreach,2,[{file,"lists.erl"},{line,1323}]},
                {rabbit_control_main,display_info_list,2,
                    [{file,"src/rabbit_control_main.erl"},{line,651}]},
                {rabbit_control_main,start,0,
                    [{file,"src/rabbit_control_main.erl"},{line,156}]},
                {init,start_it,1,[]},
                {init,start_em,1,[]}]}}
ls: cannot access /etc/rabbitmq/rabbitmq.conf.d: No such file or directory
Changing password for user "maas_longpoll" ...
...done.
ls: cannot access /etc/rabbitmq/rabbitmq.conf.d: No such file or directory
ls: cannot access /etc/rabbitmq/rabbitmq.conf.d: No such file or directory
Changing password for user "maas_workers" ...
...done.
Syncing...
Creating tables ...
Installing custom SQL ...
Installing indexes ...
Installed 0 object(s) from 0 fixture(s)

[Diogo Matsubara (matsubara)]

For the record this doesn't seem to have caused any problems with the installed MAAS

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[mlissner (mlissner-michaeljaylissner)]

Apparently this can be easily fixed by simply creating the file:

http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2013-September/030530.html

> You can create /etc/rabbitmq/rabbitmq.conf.d with rabbitmq user permissions
> to avoid this warning. If queues are listed, it has no effect on rabbitmqctl operation.

[mlissner (mlissner-michaeljaylissner)]

I just did:

    sudo mkdir /etc/rabbitmq/rabbitmq.conf.d

And tested with:

    sudo service rabbitmq-server status

Problem solved.