Re: Issues after upgrading CS from 4.1 to 4.2.1 managing XenServer 6.0.2 clusters

2014-01-17 Thread Pierre-Luc Dion
Should I test replacing xapi-5.6.100-1-20130125.183249-474.jar by the one from 4.3 branch : xapi-5.6.100-1-SNAPSHOT.jar ? Also we did not upgrade XenServer which is currently using 6.0.2. did upgrade Cloudstack from 4.1.0 to 4.2.1 Pierre-Luc Dion Architecte de Solution Cloud | Cloud Solutions

Re: Issues after upgrading CS from 4.1 to 4.2.1 managing XenServer 6.0.2 clusters

2014-01-17 Thread Wei ZHOU
same issue: CLOUDSTACK-5834 2014/1/17 Pierre-Luc Dion > Hi, > > We've upgrade our Cloudstack environment from 4.1 to 4.2.1, it is > currently managing XenServer 6.0.2 clusters. > > 1. Since we have upgraded to 4.2.1 we noticed that Secondary Storage Name > have been rename and we now see UUID's

Fwd: Issues after upgrading CS from 4.1 to 4.2.1 managing XenServer 6.0.2 clusters

2014-01-17 Thread Pierre-Luc Dion
Hi, We've upgrade our Cloudstack environment from 4.1 to 4.2.1, it is currently managing XenServer 6.0.2 clusters. 1. Since we have upgraded to 4.2.1 we noticed that Secondary Storage Name have been rename and we now see UUID's of SS. 2. On one cluster that is using local-Storage and Shared Stora