[opensuse-cloud] Re: Devstack on unsupported - RabbitMQ PAM error

After more inspection, I came to the conclusion that the install was borked for unknown reasons. I re-built a new machine using the script I posted and it just completed successfully. For anyone who wishes to install Devstack on openSUSE (and probably SLE*), I'll leave my script up at its current location. When I've verified the install is fully functional is all respects, I'll do a write-up and offer the script officially to Devstack. The script is at https://github.com/putztzu/public_scripts/blob/master/devstack_on_13.2.sh Tony On Fri, Oct 30, 2015 at 10:19 PM, Tony Su wrote:

At the moment, current focus is on an openSUSE-specific error and hopefully resolution, but am at a roadblock.

Question: Is there a trace or debug tool that can be run against BASH scripts like what is used to setup and configure Devstack?

Review of issue: Have pretty much determined that log output suggests that the Devstack installation is unable to determine the distro correctly, specifically resulting in errors running lib/rpc-backend which uninstalls, re-installs and configures RabbitMQ.

Current investigation: Have spent considerable time inspecting the architecture and much of the flow of the Devstack install. The main install script = ./stack.sh Files containing functions = function, function-common

Although openSUSE and SUSE are not officially supported by Devstack, I have found considerable existing code specific to openSUSE and SUSE, and done enough testing to verify openSUSE 13.2 and most versions of SLE* should work just fine. Have not tested TW and doubtful it would be identified properly, but that is not a current concern (am working on 13.2).

In fact, just eye-balling the code, I don't see why /lib/rpc-backend should be throwing an error, so I need a tool similar to an IDE debugger with breakpoints. Maybe instrument the BASH code with some extra echoes to stdout?

So, hoping for some advice, Thx, Tony

On Fri, Oct 30, 2015 at 8:17 PM, Tony Su wrote:

...

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 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 -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org