yes, those are the log entries I was talking about. On Tue, Dec 26, 2017 at 5:18 PM, Pierre-Luc Dion <[email protected]> wrote:
> VR creation was failing with error logs in cloudstack-management.log. I > don't have logs details in hand, is this what you are looking for ? > > I have not created a bug in Jira because it seams to be a post upgrade > XenServer issue more than CloudStack at the moment, and is easy to resolve. > > > *Pierre-Luc DION* > Architecte de Solution Cloud | Cloud Solutions Architect > t 855.652.5683 > > *CloudOps* Votre partenaire infonuagique* | *Cloud Solutions Experts > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 > w cloudops.com *|* tw @CloudOps_ > > On Tue, Dec 26, 2017 at 11:48 AM, Rafael Weingärtner < > [email protected]> wrote: > > > Did you see any exception regarding this issue to share with us? > > > > On Tue, Dec 26, 2017 at 2:12 PM, Pierre-Luc Dion <[email protected]> > > wrote: > > > > > Hi, > > > > > > Just as FYI, we recently upgrade from 6.5 to xs 7.1, so far everthing > is > > > good. Then we add some hosts to Pool or reinstall some XenServer to > have > > > proper new filesystem on dom0 which have more disk space for /var/log! > > > then we ran into the situation where CloudStack fail to create Virtual > > > Router in a XenServer cluster. Turns out that for some unknown reason, > > > adding a fresh installed xenserver to a cluster can create new SR and > VDI > > > for xs-tools iso, this break cloudstack VR creation for some reason. So > > the > > > easy fix is to forget non-shared SR containing xs-tools VDI. > > > > > > Basically, if "xe vdi-list is-tools-iso=true" return more than one iso, > > > CloudStack should fail to create Virtual-Router. > > > > > > > > > > > -- > > Rafael Weingärtner > > > -- Rafael Weingärtner
