Re: Egress rules not applied in 4.11.0

2018-04-11 Thread Martin Emrich
Hi! Am 11.04.18 um 13:38 schrieb Stephan Seitz: Hi martin, I've just read your issue on github and was wondering how you;ve been able to select Debian 9. But maybe you did a fresh installation. No, Upgrade from 4.9.2.0. I set the OS type to Debian 8 in ACS. "Debian 9.3" is what XenCenter rep

Re: Egress rules not applied in 4.11.0

2018-04-11 Thread Martin Emrich
SUK @shapeblue -Original Message- From: Stephan Seitz Sent: 11 April 2018 12:38 To: users@cloudstack.apache.org Subject: Re: Egress rules not applied in 4.11.0 Hi martin, I've just read your issue on github and was wondering how you;ve been able to select Debian 9. But maybe yo

Re: Egress rules not applied in 4.11.0

2018-04-11 Thread Stephan Seitz
t; picky > > > > > > > > > > > with different kinds of Xen virtualization as I've seen on "regular" > > VMs. > > > > > > > > > > > > > > > > > > > > > > > > > > &g

Re: Egress rules not applied in 4.11.0

2018-04-11 Thread Rafael Weingärtner
+ schrieb Paul Angus: > > > > > > > > > > > > > > > virt-what will give 'xen-domU' for paravirtualized guests. Didn't > > > XenServer make some kind of change around this as a Meltdown/Spectre > > > migation? > >

Re: Egress rules not applied in 4.11.0

2018-04-11 Thread Stephan Seitz
me kind of change around this as a Meltdown/Spectre > > migation? > > > > > > > > > > > > > > > > > > > Kind regards, > > > > > > > > Paul Angus > > > > > > > > paul.an...@shapeblue.com > >

Re: Egress rules not applied in 4.11.0

2018-04-11 Thread Rafael Weingärtner
#x27;t > XenServer make some kind of change around this as a Meltdown/Spectre > migation? > > > > > > > > > Kind regards, > > > > > > Paul Angus > > > > > > paul.an...@shapeblue.com > > > www.shapeblue.com > > &g

Re: Egress rules not applied in 4.11.0

2018-04-11 Thread Stephan Seitz
  > > www.shapeblue.com > > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK > > @shapeblue > >    > >   > > > > > > -Original Message- > > From: Stephan Seitz   > > Sent: 11 April 2018 12:38 > > To: users@cloudstack.apache.or

Re: Egress rules not applied in 4.11.0

2018-04-11 Thread Stephan Seitz
> @shapeblue >    >   > > > -Original Message- > From: Stephan Seitz   > Sent: 11 April 2018 12:38 > To: users@cloudstack.apache.org > Subject: Re: Egress rules not applied in 4.11.0 > > Hi martin, > > I've just read your issue on github and w

RE: Egress rules not applied in 4.11.0

2018-04-11 Thread Paul Angus
HSUK @shapeblue -Original Message- From: Stephan Seitz Sent: 11 April 2018 12:38 To: users@cloudstack.apache.org Subject: Re: Egress rules not applied in 4.11.0 Hi martin, I've just read your issue on github and was wondering how you;ve been able to select Debian 9. But maybe you did a fre

Re: Egress rules not applied in 4.11.0

2018-04-11 Thread Stephan Seitz
Hi martin, I've just read your issue on github and was wondering how you;ve been able to select Debian 9. But maybe you did a fresh installation. We did an update from 4.9.2 to 4.11.0 and were able to select "Debian GNU/Linux 7(64-bit)" as highest possible Debian-version. The documentation said

Re: Egress rules not applied in 4.11.0

2018-04-11 Thread Martin Emrich
I investigated further, and opened an issue: https://github.com/apache/cloudstack/issues/2561 Cheers, Martin Am 11.04.18 um 12:18 schrieb Martin Emrich: Thanks... But I think something else is now broken, too...: The SystemVMs are now no longer being provisioned: They come up "empty" with

Re: Egress rules not applied in 4.11.0

2018-04-11 Thread Martin Emrich
Thanks... But I think something else is now broken, too...: The SystemVMs are now no longer being provisioned: They come up "empty" with "systemvm type=". I also deleted the Console Proxy VM, and the new one is plain, too... I tried with Git branch 4.11 (producing 4.11.1-SNAPSHOT RPMs), same

Re: Egress rules not applied in 4.11.0

2018-04-10 Thread Rohit Yadav
Hi Martin, This is a known issue, a freshly restarted VR may not have the EGREE related tables which is why any rules will fail to apply. As a workaround, you can restart the network without selecting the cleanup option which will reconfigure the VR and add the egress table. I've a fix in th

Re: Egress rules not applied in 4.11.0

2018-04-10 Thread Martin Emrich
Hi! Am 10.04.18 um 11:09 schrieb Stephan Seitz: Hi! I think your facing a bug already discussed here. After reloading (imho doesn't matter if you check "clean up") the network, the egress rules are applied. So just reload every net with egress rules :) IIRC I tried that several times with no s

Re: Egress rules not applied in 4.11.0

2018-04-10 Thread Rafael Weingärtner
No need to open an issue ticket. There is already a PR to fix it. https://github.com/apache/cloudstack/pull/2514 On Tue, Apr 10, 2018 at 6:09 AM, Stephan Seitz wrote: > Hi! > > I think your facing a bug already discussed here. After reloading (imho > doesn't matter if you check "clean up") the n

Re: Egress rules not applied in 4.11.0

2018-04-10 Thread Stephan Seitz
Hi! I think your facing a bug already discussed here. After reloading (imho doesn't matter if you check "clean up") the network, the egress rules are applied. So just reload every net with egress rules :) Oh and don't know if that made it already to  https://github.com/apache/cloudstack/issues s