yahoo-eng-team team mailing list archive

[OpenStack Infra <1652619@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/473481
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=d5dcf1be93d9bb26bda7b375e41f03dd297888bb
Submitter: Zuul
Branch:    master

commit d5dcf1be93d9bb26bda7b375e41f03dd297888bb
Author: Radomir Dopieralski <openstack@xxxxxxxxxxxx>
Date:   Mon Jun 12 16:23:54 2017 +0200

    Allow creating ICMPV6 rules
    
    Right now, even if we specify a ::/0 (or other IPv6) CIDR in an
    ICMP rule, Horizon sets 'icmp' as the ip_protocol of that rule but
    neutron expects 'ipv6-icmp' which is the right ip_protocol for ICMPv6.
    This results in that rule never matching anything.
    
    This change makes Horizon set the ip_protocol to ipv6-icmp when
    the CIDR is an IPv6 one, and icmp when it's IPv4.
    
    Co-Authored-By: Akihiro Motoki <amotoki@xxxxxxxxx>
    Change-Id: I1f68e1e5a3e073e38ac258de5ed9c43f8acb04e9
    Closes-Bug: #1652619


** Changed in: horizon
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1652619

Title:
  Creation of ICMPV6 rule through horizon is treating as invalid packet

Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in neutron:
  Fix Committed

Bug description:
  Go to the dashboard and select the access and security for admin role
  1.Create a Security Group say SG1
  2.Select the manage rule for security Group SG1
  3.Click on ALL icmp and select the CIDR AS ::/0 for ingress and egress rule
  4.Associate to the VMs 
  5.try to ping its treating as invalid because while creating the rule for ethertype=ipv6 as icmp

  Please refer the snapshot for your reference

  Note : Same configuration through CLI works fine. 
  example :
  neutron security-group-rule-create --protocol icmpv6   --direction egress --ethertype IPv6  SG1
  neutron security-group-rule-create --protocol icmpv6   --direction ingress --ethertype IPv6  SG1

  After executing above command and its showing as icmpv6 in dashboard
  and its works fine.

  This issue is seen in stable/mitaka branch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1652619/+subscriptions