Bug #4984
onedb fsck does not detect discrepancy between UID / GID in database for resources (XML)
| Status: | Pending | Start date: | 01/16/2017 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | - | |||
| Resolution: | Pull request: | |||
| Affected Versions: | OpenNebula 4.10, OpenNebula 4.12, OpenNebula 4.14, OpenNebula 4.4, OpenNebula 4.6, OpenNebula 4.8, OpenNebula 5.0, OpenNebula 5.2 |
Description
We detected a discrepancy between the UID / GID of a VM TEMPLATE in the XML (body), and the uid / gid columns in the database. There were uid / gid values of non-existing users / groups in the database for several VM TEMPLATES. This should be found by a onedb fsck operation. To avoid creating uid / gid in the database for non-existing users in the first place (that might come into existence later on in the cloud life) a check during database operations regaring uid / gid could be incorporated.
These discrepancies are only there for resources (VM Templates) that have been created with OpenNebula 4.4.0 AFAICT (I cheched unix epoch times of VM Template and onedb upgrade (db_versioning table)).