stack update failed: port still in use

Bug #1517355 reported by huangtianhua
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OpenStack Heat
In Progress
High
ashok reddy

Bug Description

1. create a stack with template:
**********************************
heat_template_version: 2015-04-30
resources:
  s1:
    type: OS::Nova::Server
    properties:
      flavor: 1
      image: cirros-0.3.0-x86_64-disk
      networks:
      - port: {get_resource: s_port}
      - port: {get_resource: s_port2}
      name: testss
  s_port2:
    type: OS::Neutron::Port
    properties:
      network: 3447dd80-14ef-4059-8ea6-35f4fd60ba26
  s_port:
    type: OS::Neutron::Port
    properties:
      network: 3447dd80-14ef-4059-8ea6-35f4fd60ba26
**********************************
2. the stack create successful, to update the stack with template:
*******************************************
heat_template_version: 2015-04-30
resources:
  s1:
    type: OS::Nova::Server
    properties:
      flavor: 1
      image: cirros-0.3.0-x86_64-disk
      networks:
      - port: {get_resource: s_port}
      name: testss
  s2:
    type: OS::Nova::Server
    properties:
      flavor: 1
      image: cirros-0.3.0-x86_64-disk
      networks:
      - port: {get_resource: s_port2}
      name: tes2
  s_port2:
    type: OS::Neutron::Port
    properties:
      network: 3447dd80-14ef-4059-8ea6-35f4fd60ba26
  s_port:
    type: OS::Neutron::Port
    properties:
      network: 3447dd80-14ef-4059-8ea6-35f4fd60ba26
***************************************
3. the stack update failed, because the s2 create failed: port2 still in use
4. finally, we can find that port2 detached from s1

Because there is no dependence between s1 and s2, so they update in parallel. I think add the dependence to s2 will fix this problem.

Changed in heat:
assignee: nobody → huangtianhua (huangtianhua)
summary: - stack update failed
+ stack update failed: port still in use
description: updated
Changed in heat:
importance: Undecided → High
Revision history for this message
carl (gsl0610) wrote :

It seems this is not allowed in heat.
The s_port2 is fixed in the first stack creation.

zhao (hgsadjjh)
Changed in heat:
assignee: huangtianhua (huangtianhua) → zhao (hgsadjjh)
Changed in heat:
assignee: zhao (hgsadjjh) → zhaozhilong (zhaozhilong)
Changed in heat:
status: New → Confirmed
Changed in heat:
status: Confirmed → In Progress
Revision history for this message
zhaozhilong (zhaozhilong) wrote :

i meet the bug before..
when i try to update..i found my s_port2 is detached from s1...(that is OK)..
and i try to use nova interface-attach --port-id to add this port to s2..
nova give me a HTTP error(500)...

Changed in heat:
assignee: zhaozhilong (zhaozhilong) → nobody
status: In Progress → Confirmed
ashok reddy (ashokat258)
Changed in heat:
assignee: nobody → ashok reddy (ashokat258)
Revision history for this message
ashok reddy (ashokat258) wrote :

Hi zhaozhilong ,

Could you please explain this bug, In Step 1: 2 ports are assigned from same network. Is this possible? In real scenario it never be assign same 2 port from same network.

Which version of openstack did you face this issue?

Revision history for this message
Pete Birley (petebirley) wrote :

This is also affecting my deployment, Trove, Murano, and Manila are now all failing, I am running the latest heat from git, all was working well with Liberty RDO packages, and head from approx 1 month ago.

ashok reddy (ashokat258)
Changed in heat:
status: Confirmed → In Progress
Revision history for this message
pawnesh kumar (pawnesh.kumar) wrote :

i am not able to reproduce this , in newton release

Revision history for this message
david (zhr-math) wrote :

i also encounter this issue. see below error message:

Conflict: resources.server: Port c4ed7f7f-8e2a-4994-9ff1-f16da2264dba is still in use. (HTTP 409) (Request-ID: req-a814808b-54ff-461c-a1b4-1c9816c0e820)

OpenStack version is Liberty, nova version is 12.0.4.

Rico Lin (rico-lin)
Changed in heat:
milestone: none → no-priority-tag-bugs
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers