The mysql user that the guest agent uses needs to be different for HP and RAX

[Nikhil Manchanda]

The mysql user that the guest agent uses to connect to the DB needs to be different in the case of HP and RAX.
In HP's case, 'root' needs to be used, but in RAX's case 'os_admin' needs to be used.

This is a direct result of the fact that the mysql image deployed is different in the case of HP and RAX. As per Vipul's comment, RAX's implementation depends on logging into mysql to do things like add user, add database, but the HP implementation only has a root user with root access who can add users and databases by connecting on port 3306.

[Nikhil Manchanda (slicknik)]

As a temporary workaround for HP folks, you edit the file under reddwarf/reddwarf/guestagent/dbaas.py: to change the line
ADMIN_USER_NAME = "os_admin" to read
ADMIN_USER_NAME = "root"

Thanks,
-Nikhil

[Michael Basnight (hubcap)]

Lets make sure that this is an externalized user, and maybe even default it to root.

[Steve Leon (steve-leon)]

Hi Nikhil,

When making the change ADMIN_USER_NAME = "os_admin" to ADMIN_USER_NAME = "root", instance creating fails. The instance creates successfully but the guestagent fails. So using the reddwarf-cli, the instance gets stuck in "BUILD" status.

I checked the guestagent logs and it fails because mysql tries to create user "root", which fails. If i use ADMIN_USER_NAME = "os_admin", the guest agent runs successfully.

I then create users to interact with the guest mysql db.

[Nikhil Manchanda (slicknik)]

I've verified that the os_admin user works correctly for basic HP scenarios for now.
If we need to change this user to anything else, we can re-convert to a bug when the need so arises.