Open Stack

Taking another look at this issue myself,
I now have a different take on the problem.

If you compare the logs I posted,
I now am focusing on how Devstack is installing RabbitMQ, and have
probably pinpointed the problem specifically to the following script

lib/rpc_backend

and within the script the specific section

# Clean up after rpc backend -eradicate all traces so changing
backends produce a clean switch

Problem:
Probably because this is an unsupported distro, this section seems to
want to uninstall any existing rabbitmq install and thinks that the
current install is Ubuntu (it's not)

Specific Questions:
1. I don't see that "uninstall_package rabbitmq-server" points to
anything, can anyone point to where the actual uninstall routine
exists?
2. This is disappointing that the code seems to be very specific to
supported distros. Can someone provide a short explanation why
RabbitMQ should be so "clean?" Wouldn't it have made more sense to
simply replace any configuration files?
3. I don't understand the "Note" in the beginning comment about "out
of tree plugins" - Can someone provide a reference or explanation?
Googling "rabbitmq out of tree plugins" turns up nothing.

At the moment, pending any comments to this post,
Am considering commenting out everything that references any
uninstallation or installation of rabbitmq, then trying to install
again. It looks like the remaining script code assumes a systemd
architecture (exists) but I don't see specific code that sets up
authentication (a RabbitMQ password) which might be part of a custom
install.

TIA,
TSU

On Thu, Oct 29, 2015 at 9:11 AM, Tony Su <tonysu at su-networking.com> wrote:
> openSUSE 13.2
> Devstack freshly cloned from github
>
> The relevant "systemctl status" and journal entries are posted at
> http://pastebin.com/7C6vz1SA
>
> Brief Summary:
> During install, ran into RabbitMQ service failure.
> Believe that the current User credentials aren't being presented to
> RabbitMQ, which is the cause of the gnome-keyring-auth error (I
> welcome comment whether agree or disagree)
>
>
> Detailed Description of Error:
> Since this is an unsupported distro requiring "FORCE=yes ./stack.sh",
> like all other apps OpenStack uses, RabbitMQ was installed manually
> from the distro and not by the ./stack.sh script. Because of this,
> RabbitMQ is currently a default install.
>
> Reading the RabbitMQ documentation, ti looks like by default only a
> guest account is setup, but RabbitMQ in Devstack wants to use the
> credentials of the User doing the Install.
>
> I need to know which RabbitMQ backend auth plugin to use ( SSL?
> Something else?).
> Would also be cool if there is any special resource you can point me
> to, like if a config template file is simply copied.
>
> BTW - I'm curious why the RabbitMQ configuration requires the Install
> User's credentials... It would seem to me that the "sudo" identity
> should be sufficient to make configuration file edits, and different
> credentials would be used later during runtime.
>
> TIA,
> Tony