yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #35231
[Bug 1473703] [NEW] IPv6 floating IP is in Error state
Public bug reported:
IPv6 floating IP is in Error state
neutron floatingip-show 6a06b47e-4810-45a1-aac9-11b47d01d5f1
+---------------------+--------------------------------------+
| Field | Value |
+---------------------+--------------------------------------+
| fixed_ip_address | 2001:db4::f816:3eff:fe0f:cc15 |
| floating_ip_address | 2001:db8::f816:3eff:fef7:7ff8 |
| floating_network_id | fddded39-240a-488c-823d-5c5129e18d81 |
| id | 6a06b47e-4810-45a1-aac9-11b47d01d5f1 |
| port_id | 638792be-0096-4c23-bb69-680940cdd6a2 |
| router_id | cbf21934-c956-420b-862c-781511c9dd7c |
| status | ERROR |
| tenant_id | 42949b2956434b298c7adb04ac123774 |
+---------------------+--------------------------------------+
(the same with IPv4 on the same setup)
after deleting all configuration and reconfigure only v4 networks, router, VMs etc, , the new ipv4 floating IP is ACTIVE
No errors seen in log files
openstack-neutron-common-2015.1.0-10.el7ost.noarch
python-neutron-lbaas-2015.1.0-5.el7ost.noarch
openstack-neutron-openvswitch-2015.1.0-10.el7ost.noarch
python-neutron-fwaas-2015.1.0-3.el7ost.noarch
python-neutronclient-2.4.0-1.el7ost.noarch
openstack-neutron-fwaas-2015.1.0-3.el7ost.noarch
python-neutron-2015.1.0-10.el7ost.noarch
openstack-neutron-2015.1.0-10.el7ost.noarch
openstack-neutron-ml2-2015.1.0-10.el7ost.noarch
openstack-neutron-lbaas-2015.1.0-5.el7ost.noarch
** Affects: neutron
Importance: Undecided
Status: New
** Tags: ipv6
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1473703
Title:
IPv6 floating IP is in Error state
Status in neutron:
New
Bug description:
IPv6 floating IP is in Error state
neutron floatingip-show 6a06b47e-4810-45a1-aac9-11b47d01d5f1
+---------------------+--------------------------------------+
| Field | Value |
+---------------------+--------------------------------------+
| fixed_ip_address | 2001:db4::f816:3eff:fe0f:cc15 |
| floating_ip_address | 2001:db8::f816:3eff:fef7:7ff8 |
| floating_network_id | fddded39-240a-488c-823d-5c5129e18d81 |
| id | 6a06b47e-4810-45a1-aac9-11b47d01d5f1 |
| port_id | 638792be-0096-4c23-bb69-680940cdd6a2 |
| router_id | cbf21934-c956-420b-862c-781511c9dd7c |
| status | ERROR |
| tenant_id | 42949b2956434b298c7adb04ac123774 |
+---------------------+--------------------------------------+
(the same with IPv4 on the same setup)
after deleting all configuration and reconfigure only v4 networks, router, VMs etc, , the new ipv4 floating IP is ACTIVE
No errors seen in log files
openstack-neutron-common-2015.1.0-10.el7ost.noarch
python-neutron-lbaas-2015.1.0-5.el7ost.noarch
openstack-neutron-openvswitch-2015.1.0-10.el7ost.noarch
python-neutron-fwaas-2015.1.0-3.el7ost.noarch
python-neutronclient-2.4.0-1.el7ost.noarch
openstack-neutron-fwaas-2015.1.0-3.el7ost.noarch
python-neutron-2015.1.0-10.el7ost.noarch
openstack-neutron-2015.1.0-10.el7ost.noarch
openstack-neutron-ml2-2015.1.0-10.el7ost.noarch
openstack-neutron-lbaas-2015.1.0-5.el7ost.noarch
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1473703/+subscriptions
Follow ups