OpenStack Heat

Failing FIP resources in Heat integration tests job

Bug #1449896 reported by Sergey Kraynev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Fix Released
Critical
Sergey Kraynev
OpenStack Heat 5.0.0 "liberty"

Bug Description

2015-04-29 00:56:21.005 | 2015-04-29 00:56:20.967 | Captured traceback:
2015-04-29 00:56:21.006 | 2015-04-29 00:56:20.968 | ~~~~~~~~~~~~~~~~~~~
2015-04-29 00:56:21.009 | 2015-04-29 00:56:20.971 | Traceback (most recent call last):
2015-04-29 00:56:21.011 | 2015-04-29 00:56:20.972 | File "/opt/stack/new/heat/heat_integrationtests/scenario/test_neutron_loadbalancer.py", line 66, in test_neutron_loadbalancer
2015-04-29 00:56:21.052 | 2015-04-29 00:56:21.013 | parameters=parameters
2015-04-29 00:56:21.053 | 2015-04-29 00:56:21.015 | File "/opt/stack/new/heat/heat_integrationtests/scenario/scenario_base.py", line 54, in launch_stack
2015-04-29 00:56:21.056 | 2015-04-29 00:56:21.018 | expected_status=expected_status
2015-04-29 00:56:21.062 | 2015-04-29 00:56:21.023 | File "/opt/stack/new/heat/heat_integrationtests/common/test.py", line 382, in stack_create
2015-04-29 00:56:21.063 | 2015-04-29 00:56:21.025 | self._wait_for_stack_status(**kwargs)
2015-04-29 00:56:21.089 | 2015-04-29 00:56:21.027 | File "/opt/stack/new/heat/heat_integrationtests/common/test.py", line 269, in _wait_for_stack_status
2015-04-29 00:56:21.089 | 2015-04-29 00:56:21.028 | stack_status_reason=stack.stack_status_reason)
2015-04-29 00:56:21.089 | 2015-04-29 00:56:21.030 | heat_integrationtests.common.exceptions.StackBuildErrorException: Stack NeutronLoadBalancerTest-364003098/3efac61b-23f4-4b37-82c1-4b53dbc6c8c4 is in CREATE_FAILED status due to 'Resource CREATE failed: ResourceInError: Went to status ERROR due to "error in vip"'
2015-04-29 00:56:21.090 | 2015-04-29 00:56:21.031 |
2015-04-29 00:56:39.784 | 2015-04-29 00:56:39.745 | {0} heat_integrationtests.scenario.test_server_cfn_init.CfnInitIntegrationTest.test_server_cfn_init [18.780556s] ... FAILED
2015-04-29 00:56:39.787 | 2015-04-29 00:56:39.748 |
2015-04-29 00:56:39.790 | 2015-04-29 00:56:39.750 | Captured traceback:
2015-04-29 00:56:39.792 | 2015-04-29 00:56:39.754 | ~~~~~~~~~~~~~~~~~~~
2015-04-29 00:56:39.794 | 2015-04-29 00:56:39.756 | Traceback (most recent call last):
2015-04-29 00:56:39.795 | 2015-04-29 00:56:39.757 | File "/opt/stack/new/heat/heat_integrationtests/scenario/test_server_cfn_init.py", line 109, in test_server_cfn_init
2015-04-29 00:56:39.797 | 2015-04-29 00:56:39.759 | self.check_stack(stack_id)
2015-04-29 00:56:39.824 | 2015-04-29 00:56:39.761 | File "/opt/stack/new/heat/heat_integrationtests/scenario/test_server_cfn_init.py", line 32, in check_stack
2015-04-29 00:56:39.824 | 2015-04-29 00:56:39.763 | sid, res, 'CREATE_COMPLETE')
2015-04-29 00:56:39.824 | 2015-04-29 00:56:39.764 | File "/opt/stack/new/heat/heat_integrationtests/common/test.py", line 230, in _wait_for_resource_status
2015-04-29 00:56:39.824 | 2015-04-29 00:56:39.766 | resource_status_reason=res.resource_status_reason)
2015-04-29 00:56:39.824 | 2015-04-29 00:56:39.767 | heat_integrationtests.common.exceptions.StackResourceBuildErrorException: Resource IPAddress in stack CfnInitIntegrationTest-1351715510/a609decb-9e8c-4de3-b96e-0729cb5b7c1a is in CREATE_FAILED status due to 'BadRequest: Unable to associate floating ip 172.24.5.4 to any fixed IPs for instance 981d1ff6-7226-494e-8c29-cd662888b152. Instance has no fixed IPv4 addresses to associate. (HTTP 400) (Request-ID: req-f7ec6be5-a6c2-4723-bdbd-6b0205925bb3)'

Revision history for this message
Rabi Mishra (rabi) wrote :

Rather than an fip issue, It seems like instances are not getting fixed ip. Therefore this is failing.

Revision history for this message
Sergey Kraynev (skraynev) wrote :

Rabi: correct. paste from n-api log:

{"ports": [{"status": "ACTIVE", "name": "", "allowed_address_pairs": [], "admin_state_up": true, "network_id": "00faf2fd-d532-4415-9b91-c823971a63f2", "tenant_id": "4853503b98b940b7b5431436d2407925", "extra_dhcp_opts": [], "binding:vnic_type": "normal", "device_owner": "compute:None", "mac_address": "fa:16:3e:8f:de:17", "fixed_ips": [{"subnet_id": "1fe093ed-9cc7-4303-b49f-ba9151c558bc", "ip_address": "fdbf:e4f:8f29:0:f816:3eff:fe8f:de17"}], "id": "3af29933-73ff-40eb-a664-918da024be32", "security_groups": ["5b2db96a-185b-445a-8e0a-b8db7e8b2802"], "device_id": "981d1ff6-7226-494e-8c29-

where "fixed_ips": [{"subnet_id": "1fe093ed-9cc7-4303-b49f-ba9151c558bc", "ip_address": "fdbf:e4f:8f29:0:f816:3eff:fe8f:de17"}]

Note, that it works for me on the today's devstack.

Revision history for this message
Sergey Kraynev (skraynev) wrote :

Aha. the issue is related with Subnet. Currently devstack creates two subnets (ipv4 and ipv6). In our test we assign vms it on subnet with ipv6. So need to choose it carefully

Revision history for this message
Steven Hardy (shardy) wrote :

Confirmed, I'm seeing this too - it appears to be breaking the gate for all changes? Therefore raising to critical.

Changed in heat:
status: New → Confirmed
importance: High → Critical
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to heat (master)

Fix proposed to branch: master
Review: https://review.openstack.org/178576

Changed in heat:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to heat (master)

Reviewed: https://review.openstack.org/178576
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=368962044bdbdd3463c4277f7e078eb586c6fcee
Submitter: Jenkins
Branch: master

commit 368962044bdbdd3463c4277f7e078eb586c6fcee
Author: Sergey Kraynev <email address hidden>
Date: Wed Apr 29 05:31:54 2015 -0400

    Use ipv4 subnet in Heat scenario tests

    Previously we used first subnet from network and it was correct, because
    there was only one subnet in network by default. According to the last changes
    in devstack new ipv6 subnet was added to the all default networks.
    This patch adds function to the base class, which allows to choose
    subnet based on ip version. All scenario tests were updated to use only ipv4
    subnet.

    Also was added property for FIP, which specify ip of vip.

    Change-Id: I199075909b97fe98e1a3c1d175b0b4cf7100403d
    Closes-Bug: #1449896

Changed in heat:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in heat:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in heat:
milestone: liberty-1 → 5.0.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.