Bug #5458
Import datastores without any vcenter cluster
| Status: | Closed | Start date: | 10/13/2017 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Sergio Semedi | % Done: | 100% | |
| Category: | vCenter | |||
| Target version: | Release 5.4.3 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 5.4.2 |
Description
It is possible to import datastores without any Vcenter cluster associated to opennebula.
this leads into failures due to the connection beetwen datastore and cluster.
Associated revisions
B #5458: onevcenter does not allow to import without a valid cluster, sunstone cache invalidation (#532)
- B #5458: onevcenter does not allow to import resources without a valid cluster
- B #5458: onevcenter does not allow to import nets without a valid cluster
- B #5458: sunstone gui cache invalidation
(cherry picked from commit a39d1529819a76d8e72bb99de96011a8d8caf1a9)
B #5458: onevcenter does not allow to import without a valid cluster, sunstone cache invalidation (#532)
- B #5458: onevcenter does not allow to import resources without a valid cluster
- B #5458: onevcenter does not allow to import nets without a valid cluster
- B #5458: sunstone gui cache invalidation
(cherry picked from commit a39d1529819a76d8e72bb99de96011a8d8caf1a9)
History
#1
Updated by Sergio Semedi over 3 years ago
Also it should be mandatory that every vcenter host imported to opennebula has his own opennebula cluster to avoid future problems.
#2
Updated by Sergio Semedi over 3 years ago
- % Done changed from 0 to 100
#3
Updated by OpenNebula Systems Support Team over 3 years ago
Needs documentation
#4
Updated by OpenNebula Systems Support Team over 3 years ago
- Status changed from Assigned to Closed
- Resolution set to fixed