You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Jean-Francois Nadeau <th...@gmail.com> on 2018/11/04 21:14:45 UTC
Problem creating networks after 4.11 upgrade
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
Re: Problem creating networks after 4.11 upgrade
Posted by Jean-Francois Nadeau <th...@gmail.com>.
Hi Paul,
Thanks you on the precision about voting. I wasn't sure this was the right
place to rise blockers for targeted use cases. And in regards to the
issue, I do get the same error creating a shared network that is not scoped
to a project.
On Mon, Nov 5, 2018 at 8:09 AM Paul Angus <pa...@shapeblue.com> wrote:
> Hi Eric & Jean-Francois,
> Thanks for your work in testing.
> There is an open vote, could you now (and in future) respond to the
> thread, the official vote will/would pass as it stands. (I only caught this
> through doing a final sweep of the mailing lists).
>
> @Jean-Francois Nadeau is your error specifically related to creating
> shared networks in *projects* ?
>
> @eric please could you document the specific issues that you found, so
> that we can try to replicate and fix them
>
> Kind regards,
>
> Paul Angus
>
> paul.angus@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London WC2E 9DPUK
> @shapeblue
>
>
>
>
> -----Original Message-----
> From: Eric Lee Green <er...@gmail.com>
> Sent: 04 November 2018 21:29
> To: users@cloudstack.apache.org
> Subject: Re: Problem creating networks after 4.11 upgrade
>
> 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
> >
>
>
RE: Problem creating networks after 4.11 upgrade
Posted by Paul Angus <pa...@shapeblue.com>.
Hi Eric & Jean-Francois,
Thanks for your work in testing.
There is an open vote, could you now (and in future) respond to the thread, the official vote will/would pass as it stands. (I only caught this through doing a final sweep of the mailing lists).
@Jean-Francois Nadeau is your error specifically related to creating shared networks in *projects* ?
@eric please could you document the specific issues that you found, so that we can try to replicate and fix them
Kind regards,
Paul Angus
paul.angus@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London WC2E 9DPUK
@shapeblue
-----Original Message-----
From: Eric Lee Green <er...@gmail.com>
Sent: 04 November 2018 21:29
To: users@cloudstack.apache.org
Subject: Re: Problem creating networks after 4.11 upgrade
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
>
Fwd: Problem creating networks after 4.11 upgrade
Posted by Jean-Francois Nadeau <th...@gmail.com>.
+dev
this is a considered blocker for an upgrade to 4.11.2 (at least for us):
https://github.com/apache/cloudstack/issues/2989
---------- Forwarded message ---------
From: Jean-Francois Nadeau <th...@gmail.com>
Date: Mon, Nov 5, 2018 at 7:21 AM
Subject: Re: Problem creating networks after 4.11 upgrade
To: <us...@cloudstack.apache.org>
Test was on 4.11.2rc3. will send to dev list
Re: Problem creating networks after 4.11 upgrade
Posted by Jean-Francois Nadeau <th...@gmail.com>.
Test was on 4.11.2rc3. will send to dev list
Re: Problem creating networks after 4.11 upgrade
Posted by Andrija Panic <an...@gmail.com>.
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.green@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
> >
>
>
Re: Problem creating networks after 4.11 upgrade
Posted by Eric Lee Green <er...@gmail.com>.
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
>