RE: [ACS44] CLOUDSTACK-6464
Daan, Thanks for following up. Both Marcus and Edison have been involved looking at this bug, and it appears to be related to what CS expects in the cloud.vlan table between releases. This issue affects both untagged networks and tagged networks in the same manner, and simply changing the vlan_id column data format seems to fix the problem. A couple of us (myself included) have tested a database fix and commented success in the issue notes. Since our testing, I haven't seen any comment on how this should be fixed permanently (either a database data change during upgrade, or code to support the older data format for original installs prior to 4.3). My preference would be a data change, as that's easier to maintain moving forward. I still think a note should be posted on 4.3, suggesting people to avoid it for KVM upgrades, or at the very least pointing them to this issue so they can updated the data format manually post upgrade, and prior to restarting their VRs. - Si From: Daan Hoogland daan.hoogl...@gmail.com Sent: Thursday, June 12, 2014 8:47 AM To: dev Subject: Re: [ACS44] CLOUDSTACK-6464 Simon, I found you in my spam box looking for my colleague, Hugo. Didn't find him there;) I guess you're request is no longer actual, The bug is, no doubt. Can you give an update on it? On Wed, May 14, 2014 at 1:00 AM, Simon Weller swel...@ena.com wrote: All, Could someone with knowledge of the KVM traffic label code take a look at https://issues.apache.org/jira/browse/CLOUDSTACK-6464? It appears egress traffic is broken currently when basic or advanced networking is in use with traffic labels on KVM. Daan, Could you change the tag for this to 4.4 from 4.3.1, and in my opinion this should be a blocker, as it completely breaks KVM VR networking. Thanks, - Si -- Daan
Re: [ACS44] CLOUDSTACK-6464
ok, please note discussions on 4.3.1 and my comment in it. The db upgrade solution will go in the alleged 4.3.1! I changed the bug to fix-version 4.4.0 but will put it back to 4.3.1. It is solved this way in the coming 4.4.0 as well. On Fri, Jun 13, 2014 at 2:54 PM, Simon Weller swel...@ena.com wrote: Daan, Thanks for following up. Both Marcus and Edison have been involved looking at this bug, and it appears to be related to what CS expects in the cloud.vlan table between releases. This issue affects both untagged networks and tagged networks in the same manner, and simply changing the vlan_id column data format seems to fix the problem. A couple of us (myself included) have tested a database fix and commented success in the issue notes. Since our testing, I haven't seen any comment on how this should be fixed permanently (either a database data change during upgrade, or code to support the older data format for original installs prior to 4.3). My preference would be a data change, as that's easier to maintain moving forward. I still think a note should be posted on 4.3, suggesting people to avoid it for KVM upgrades, or at the very least pointing them to this issue so they can updated the data format manually post upgrade, and prior to restarting their VRs. - Si From: Daan Hoogland daan.hoogl...@gmail.com Sent: Thursday, June 12, 2014 8:47 AM To: dev Subject: Re: [ACS44] CLOUDSTACK-6464 Simon, I found you in my spam box looking for my colleague, Hugo. Didn't find him there;) I guess you're request is no longer actual, The bug is, no doubt. Can you give an update on it? On Wed, May 14, 2014 at 1:00 AM, Simon Weller swel...@ena.com wrote: All, Could someone with knowledge of the KVM traffic label code take a look at https://issues.apache.org/jira/browse/CLOUDSTACK-6464? It appears egress traffic is broken currently when basic or advanced networking is in use with traffic labels on KVM. Daan, Could you change the tag for this to 4.4 from 4.3.1, and in my opinion this should be a blocker, as it completely breaks KVM VR networking. Thanks, - Si -- Daan -- Daan
Re: [ACS44] CLOUDSTACK-6464
Simon, I found you in my spam box looking for my colleague, Hugo. Didn't find him there;) I guess you're request is no longer actual, The bug is, no doubt. Can you give an update on it? On Wed, May 14, 2014 at 1:00 AM, Simon Weller swel...@ena.com wrote: All, Could someone with knowledge of the KVM traffic label code take a look at https://issues.apache.org/jira/browse/CLOUDSTACK-6464? It appears egress traffic is broken currently when basic or advanced networking is in use with traffic labels on KVM. Daan, Could you change the tag for this to 4.4 from 4.3.1, and in my opinion this should be a blocker, as it completely breaks KVM VR networking. Thanks, - Si -- Daan
