Could you please try with 4.11.2 RC release? Did you send an email on DEV list with link to GitHub?
On Sun, Nov 4, 2018, 22:29 Eric Lee Green <eric.lee.gr...@gmail.com wrote: > Yeah, had all sorts of problems with custom network offerings after > upgrading to 4.11.1, along with problems with launching virtual machines > (every attempt to launch resulted in a "not enough resources" error), > couldn't get virtual routers to come up for custom networks, etc. I > didn't have time in my service window to do any detailed examinations of > why they were failing, I just downgraded back to 4.9.2 before my service > window ended. When 4.11 is stable, maybe I'll try upgrading to it again. > (OS: Centos 7. Old version: 4.9.2. New version: 4.11.1. Hardware: Three > compute servers with dual hexacore processors and 96gb+ of memory w/KVM. > End result after two hours of trying to make it work: Downgrade back to > 4.9.2.) > > I was thinking about migrating most of my other computer servers into > the Cloudstack cloud because it's easier for my users to take care of > their own resources, but I was hoping to do it after migrating to 4.11. > I guess not. > > On 11/4/18 13:14, Jean-Francois Nadeau wrote: > > > I all, > > > > I was wondering if anyone else had this problem after upgrading from 4.9. > > All our networks are using a custom network offering with no services > > defined since the physical network provides DHCP and DNS. Environment > is > > CentOS 7, KVM with the openvswitch driver. > > > > Now after the upgrade to 4.11, creating a network using that same > network > > offering fails with an "Unable to convert network offering with > specified > > id to network profile" error. > > > > The issue is documented here: > > https://github.com/apache/cloudstack/issues/2989 > > > > I hope someone can have a look at it. This is the last issue that blocks > > us from upgrading. > > > > best, > > > > Jean-Francois > > > >