[NETVIRT-212] Instance not assigned IP when using Security rule for ICMPV6 Created: 25/Oct/16  Updated: 09/Mar/18  Resolved: 01/Nov/16

Status: Resolved
Project: netvirt
Component/s: None
Affects Version/s: Boron
Fix Version/s: None

Type: Bug
Reporter: Venkatrangan Govindarajan Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 7015
Priority: Highest

 Description   

Steps to reproduce the problem

a. Create a new security group

b. Add security rules to allow icmp and icmpv6

c. Create Network/Subnet

d. Create isntance and specify the security group that was created

e. Verify the instance console log, the instance is not assigned any IP Address.

 Comments   
Comment by Venkatrangan Govindarajan [ 25/Oct/16 ]

Patches currently ready for review and merge

https://git.opendaylight.org/gerrit/#/c/47358/

https://git.opendaylight.org/gerrit/#/c/47422/

Comment by Venkatrangan Govindarajan [ 25/Oct/16 ]

Note: Horizon does not allow adding IPV6 rules, The same needs to be done using CLI

eg:
neutron security-group-rule-create csit --direction ingress --ethertype IPv6 --protocol icmpv6

Comment by A H [ 25/Oct/16 ]

A patch was submitted to fix this bug in Boron SR1: https://git.opendaylight.org/gerrit/#/c/47358/

To better assess the impact of this bug and fix, could someone from your team please help us identify the following:
Severity: Could you elaborate on the severity of this bug? Is this a BLOCKER such that we cannot release Beryllium without it? Is there a workaround such that we can write a release note?
Testing: Could you also elaborate on the testing of this patch? How extensively has this patch been tested? Is it covered by any unit tests or system tests?
Impact: Does this fix impact any dependent projects?

Comment by Sam Hague [ 26/Oct/16 ]

b: https://git.opendaylight.org/gerrit/47358
c: https://git.opendaylight.org/gerrit/47422

Comment by A H [ 28/Oct/16 ]

For the record, the severity/testing/impact analysis for this bug can be found here:

https://lists.opendaylight.org/pipermail/netvirt-dev/2016-October/001870.html

Comment by A H [ 01/Nov/16 ]

Has this bug been verified as fixed in the latest Boron SR1 Build 20161030?

Comment by Venkatrangan Govindarajan [ 01/Nov/16 ]

(In reply to A H from comment #6)
> Has this bug been verified as fixed in the latest Boron SR1 Build 20161030?

An,

Yes it was tested in sandbox in this run

https://jenkins.opendaylight.org/sandbox/job/netvirt-csit-1node-openstack-mitaka-openstack-boron/13/console

Log: https://logs.opendaylight.org/sandbox/jenkins091/netvirt-csit-1node-openstack-mitaka-openstack-boron/13/archives/log.html.gz

Generated at Wed Feb 07 20:20:59 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.