This sounds like a bug in 4.15 upgrade process, assuming Cristian is NOT using vVols (which were not even supported pre-4.15)
Can you please log a bug, describing your VMware and storage setup? Best, On Fri, 22 Jan 2021 at 07:39, <cristian.c@istream.today> wrote: > Hi Nicolas, > > Thank you for your answer, I just created the "fcd" folder and now it > works fine! > > I'm using the version 6.5, u3 for vCenter and hosts. > > > Regards, > Cristian > > -----Original Message----- > From: Nicolas Vazquez <nicolas.vazq...@shapeblue.com.INVALID> > Sent: Friday, January 22, 2021 7:12 AM > To: users@cloudstack.apache.org > Subject: Re: fcd was not found - after upgrade to 4.15 > > Hi Cristian, > > CloudStack 4.15 introduces support for Vmware advanced capabilities in > which it is included the support for vVols. It is not possible to create > disks under the root directory of primary storage pools for this type of > storage, so the fcd folder is created. Can you please create this directory > on your primary storage and retry the VR upgrade? Which Vmware version are > your hosts and vCenter running? > > > Regards, > > Nicolas Vazquez > > ________________________________ > From: cristian.c@istream.today <cristian.c@istream.today> > Sent: Thursday, January 21, 2021 11:52 AM > To: users@cloudstack.apache.org <users@cloudstack.apache.org> > Subject: fcd was not found - after upgrade to 4.15 > > Hello, > > > > Today we upgraded one of our cloudstack environment from 4.14 to > 4.15 ( with vmware ) and we have found out that we are not able to upgrade > the routers because of this error; clone volume from base image failed due > to > Exception: java.lang.RuntimeException > > Message: File [Datastore] fcd/ was not found. > > > > Any idea why? > > > > full log : https://pastebin.com/nVrexSa4 > > > > > > Regards, > > Cristian > > > nicolas.vazq...@shapeblue.com > www.shapeblue.com > 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK > @shapeblue > > > > > -- Andrija Panić
