Opennebula database boostraping issue after first reboot
|Affected Versions:||OpenNebula 4.12|
Dear OpenNebula developers
We are testing the new opennebula 4.12 and we found an issue when you switch to a new database. After the package installation Opennebula uses sqlite db backend and generates new *_auth files.
The problem is when you want to switch to mysql db and generate a new db from scratch, the db schema is generated correctly but users_pool table is empty and oned service fails. From oned logs:
Fri Jun 5 15:54:38 2015 [Z0][ONE][I]: Log level:3 [0=ERROR,1=WARNING,2=INFO,3=DEBUG]
Fri Jun 5 15:54:38 2015 [Z0][ONE][I]: Support for xmlrpc-c > 1.31: yes
Fri Jun 5 15:54:38 2015 [Z0][ONE][I]: Checking database version.
Fri Jun 5 15:54:38 2015 [Z0][ONE][I]: Bootstrapping OpenNebula database, stage 1.
Fri Jun 5 15:54:39 2015 [Z0][ONE][I]: Bootstrapping OpenNebula database, stage 2.
Fri Jun 5 15:54:39 2015 [Z0][ACL][I]: Starting ACL Manager...
Fri Jun 5 15:54:39 2015 [Z0][ACL][I]: ACL Manager started.
Fri Jun 5 15:54:39 2015 [Z0][ONE][E]: Password file /var/lib/one//.one/sunstone_auth already exists but OpenNebula is boostraping the database. Check your database
The only workaround is to remove *_auth files fom /var/lib/one/.one dir (and keep one_auth file). In that case the opennebula database is generated correctly.
Is this a known issue? we didn't have this problem before.
Thanks in advance
#1 Updated by Ruben S. Montero about 6 years ago
- Status changed from Pending to Closed
- Resolution set to worksforme
This is in fact the expected behavior, when bootstraping opennebula will overwrite saved passwords. This behavior was introduced to prevent oned overwriting existing passwords; as was a situation that may occurs when upgrading and for example using a non-updated oned.