[NEUTRON-116] Null values received on neutron security-group-rule-delete and security-group-delete Created: 09/Mar/16 Updated: 19/Oct/17 Resolved: 03/Aug/16 |
|
| Status: | Resolved |
| Project: | neutron |
| Component/s: | neutron-spi |
| Affects Version/s: | Multiple |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Tomas Cechvala | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Attachments: |
|
| External issue ID: | 5478 |
| Priority: | Highest |
| Description |
|
The problem occur when working with liberty devstack. How to reproduce: 1) neutron security-group-create sg1 When deleting neutron security group rules, NeutronSecurityRule object is null in neutronSecurityRuleDeleted method. 2) neutron security-group-create sg1 This also happens when deleting security groups. Security rules in NeutronSecurityGroup object are also null in neutronSecurityGroupDeleted method. |
| Comments |
| Comment by Tomas Cechvala [ 09/Mar/16 ] |
|
on #2 |
| Comment by Isaku Yamahata [ 10/Mar/16 ] |
|
This seems like related to https://bugs.opendaylight.org/show_bug.cgi?id=4550 So can you please try For Boron, the direction is to delete securitygroup::securitygrouprules because |
| Comment by Isaku Yamahata [ 12/Mar/16 ] |
|
The patch was merged into master branch.
If your code is using MD-SAL, you need to listen to data change notification of security rules in addition to security-group rules. and check security-rule:security-group-id. In boron cycle, security-group:security-rules will be deleted. |
| Comment by Tomas Cechvala [ 15/Mar/16 ] |
|
Attachment command sequence.txt has been added with description: Devstack commands |
| Comment by Tomas Cechvala [ 15/Mar/16 ] |
|
Attachment mikita-beryllium_karaflog.log has been added with description: karaf.log |
| Comment by Tomas Cechvala [ 15/Mar/16 ] |
|
Attachment mikita-master_karaflog.log has been added with description: karaf.log |
| Comment by Tomas Cechvala [ 15/Mar/16 ] |
|
Attachment mikita-master_karaflog_patch33957.log has been added with description: karaf log |
| Comment by Tomas Cechvala [ 15/Mar/16 ] |
|
I'm not quite sure if I follow, let me attach karaf.log for more info. When removing a security-group, it’s rules are missing in NeutronSecurityGroup object. Please notice canDeleteNeutronSecurityGroup message When removing just a rule, it comes to us as null. Please notice canDeleteNeutronSecurityRule. It behaves the same in master and beryllium. Unfortunately patch https://git.opendaylight.org/gerrit/#/c/33957 didn't change this behavior. |
| Comment by Isaku Yamahata [ 15/Mar/16 ] |
|
what version of networking-odlare you using? Does it include the merged patch into master? Can you please provide the packet capture between networking-odl and ODL? |
| Comment by Isaku Yamahata [ 15/Mar/16 ] |
|
With Beryllium, did you apply the patch to beryllium branch? Can you please check it? |
| Comment by Isaku Yamahata [ 15/Mar/16 ] |
|
For beryllium, the proposed patch is found at |
| Comment by Dileep Ranganathan [ 19/Mar/16 ] |
|
Patch for handling the default rules associated with a security group |
| Comment by Tomas Cechvala [ 21/Mar/16 ] |
|
The problem still persits, I checked out neutron beryllium patch https://git.opendaylight.org/gerrit/#/c/34586 Networking-odl master patch was included as well I'm not sure if packet capture can get us closer, but i'm going to attach it. The following features should be installed |
| Comment by Tomas Cechvala [ 21/Mar/16 ] |
|
What i've tried neutron net-create net1 (just to test logging) logs looks the same as before. |
| Comment by Tomas Cechvala [ 21/Mar/16 ] |
|
192.168.50.1 - ODL, 192.168.50.20 - Devstack Control Node |
| Comment by Tomas Cechvala [ 21/Mar/16 ] |
|
Attachment testing_sg.pcap has been added with description: Wireshark capture on devstack-control |
| Comment by Isaku Yamahata [ 21/Mar/16 ] |
|
Thanks, the remaining issues is null as NeutornSecurityRule.
details: It will be addressed by the following patch. As stable/beryllium which support liberty, the work around patch will be needed. |
| Comment by Tomas Cechvala [ 23/Mar/16 ] |
|
I've tested mitaka-boron with neutron patch (already in master): networking-odl patch: I don't recommend to merge networking-odl patch. An exception occurred in ODL everytime security-group was created (neutron security-group-create sg-name). Please, see error message. I tried to test again but without networking-odl patch. |
| Comment by Tomas Cechvala [ 23/Mar/16 ] |
|
Attachment error_in_log.txt has been added with description: error after neutron security-group-create sg123 |
| Comment by Tomas Cechvala [ 30/Mar/16 ] |
|
I've just tested again with |
| Comment by Isaku Yamahata [ 30/Mar/16 ] |
|
@Tomas, thank you for test. |
| Comment by Isaku Yamahata [ 03/Aug/16 ] |
|
As it's tested and there is no further comments. let's close this. |