Bug #2839
onedb fsck complains about multiple system datastores and removes from cluster
| Status: | Closed | Start date: | 04/17/2014 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: |  Carlos Martín | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | Release 4.6 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 4.4 |
Description
When we have multiple system datastores in a cluster,
onedb fsck complains about that and removes them from cluster,
except one:
System Datastore 101 is in Cluster 105, but it already contains System Datastore 102 Datastore 101 is in Cluster 105 datastore id list, but it should not
I this case we have cluster 105 with 2 system datastores 101 and 102.
After onedb fsck datastore 102 is removed from clustre 105.
Associated revisions
Bug #2839: Fsck now allows multiple system DS in the same cluster
Bug #2839: Fsck now allows multiple system DS in the same cluster
(cherry picked from commit 544d155fbbf438e59fe88089bc9e46ebb8113bf6)
History
#1
Updated by Ruben S. Montero about 7 years ago
- Assignee set to Carlos Martín
- Target version set to Release 4.6
#2
Updated by Carlos Martín about 7 years ago
- Status changed from Pending to Closed
- Resolution set to fixed
It's now fixed in the repo, and the documentation has instructions to update the fsck shipped with 4.4.
Thanks!