onedb does not work password with special characters.
|Assignee:||Carlos Martín||% Done:|
|Target version:||Release 3.0|
|Affected Versions:||OpenNebula 3.0|
My mysql database password contains
and #. When I tried to run "onedb history" command to upgrade from one-3beta1 to beta2, it failed indicating password confusion caused by and #.
After I changed my password to one without @ or #, the onedb commands work as expected.
It would be good to fix this since the oned command does not have a problem with these special characters at all.
I guess this is because they use different ruby database backends, sequel from gem vs ruby-mysql.
Not sure if you can fix it at the onedb command level or have to go upstream to sequel.
Still, it would be nice to be consistent.
#3 Updated by Carlos Martín almost 10 years ago
The onedb command relies on the sequel gem, and I don't see any easy way to solve this from our code.
I'd say it is reasonable to leave this bug as a known issue, since the workaround is quite easy.
To change the oneadmin's password, the set password statement can be used:
$ mysql -u oneadmin -p mysql> SET PASSWORD = PASSWORD('newpass');
#4 Updated by Shi Jin almost 10 years ago
Yes, this is exactly what I expected.
It is interesting to me though that the core OpenNebula does not have this problem since it is using ruby-mysql.
Also, I think a different ruby mysql engine is used for the oZone part.
I am curious what is the cause of using 3 different mysql interface within a single project.