search

turbonomic / kubeturbo

140 stars 75 forks source link

The ID for quota (VDC) #144

Closed songbinliu closed 6 years ago

songbinliu commented 6 years ago

In current implementation, quota ID is name of the namespace. This may cause error if there are several kubernetes targets are added to OpsMgr.

DongyiYang commented 6 years ago

As well as in a federated cluster.

songbinliu commented 6 years ago

The short UID of namespace causes clashes in OpsMgr:

2018-02-14 17:10:58,485  WARN [Discovery Thread Pool #5] [FluentAPI]    : Kubernetes-https://openshift.119:8443.1b : Object creation clash: For target Kubernetes-https://openshift.119:8443.1b: Attempted to create a VirtualDataCenter type object with name ste and UUID ste. An object with the type User, name ste, display name ste and UUID _ERDJcBHREei_JJ3170yICw is already in the registry
2018-02-14 17:10:58,485 ERROR [Discovery Thread Pool #5] [EntityParser] : Exception while creating SE: ste
com.vmturbo.platform.VMTRoot.ManagedEntities.Abstraction.FluentAPI.ClashingObjectsException: Kubernetes-https://openshift.119:8443.1b : Object creation clash: For target Kubernetes-https://openshift.119:8443.1b: Attempted to create a VirtualDataCenter type object with name ste and UUID ste. An object with the type User, name ste, display name ste and UUID _ERDJcBHREei_JJ3170yICw is already in the registry
    at com.vmturbo.platform.VMTRoot.ManagedEntities.Abstraction.FluentAPI.DiscoveryContextImpl.clashObjectNewObjectDuplicateUuid(DiscoveryContextImpl.java:387) ~[com.vmturbo.platform-6.1.0-SNAPSHOT.jar:?]

And in UI, won't able to find the VDC ste.