Bug #1694
System datastore can in fact be added to cluster
| Status: | Closed | Start date: | 12/14/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | Release 4.0 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 3.8 |
Description
(255) one $ onecluster adddatastore 171 0
[ClusterAddDatastore] Cannot add object to cluster. Datastore 'system' cannot be added to any cluster.
ID NAME CLUSTER IMAGES TYPE TM(255) one $ onedatastore list
0 system 798YIUHLKIJ 0 - ssh
one $ onecluster deldatastore 171 0
[ClusterDelDatastore] Cannot remove object from cluster. Datastore ID is not part of the cluster set.
ID NAME CLUSTER IMAGES TYPE TM(255) one $ onedatastore list
0 system - 0 - ssh
Associated revisions
Bug #1694: Rollback cluster id when system DS is added to any cluster
Bug #1694: Add new attribute system_ds to Cluster. Template attribute is now ignored
Bug #1694: Remove potential deadlock
Bug #1694: If a DS updates its type to system_ds, update the cluster system_ds
Bug #1694: onedb migrator
Bug #1694: FSCK checks the system_ds is part of the cluster, and that there are not more than one system ds per cluster
Revert "Bug #1694: If a DS updates its type to system_ds, update the cluster system_ds"
This reverts commit ca4504f984d65ed9500dbd08ac530d6b2ae7ed99.
bug #1694: recover change from reverted commit
bug #1694: Use datastore ID in error message
bug #1694: Fix memory leak when updating templates with syntax errors
bug #1694: Move check logic for datastores to update function
History
#1
Updated by Ruben S. Montero over 8 years ago
- Category set to Core & System
- Status changed from New to Closed
- Target version set to Release 4.0
- Resolution set to fixed