yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #60081
[Bug 1652619] [NEW] Creation of ICMPV6 rule through horizon is treating as invalid packet
Public bug reported:
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.
** Affects: horizon
Importance: Undecided
Status: New
** Attachment added: "snapshot of icmpv6_config"
https://bugs.launchpad.net/bugs/1652619/+attachment/4796540/+files/icmp_type.JPG
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1652619
Title:
Creation of ICMPV6 rule through horizon is treating as invalid packet
Status in OpenStack Dashboard (Horizon):
New
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
Follow ups