[NETVIRT-832] Instance fails to start when using a previously used port Created: 09/Aug/17  Updated: 03/May/18  Resolved: 06/Apr/18

Status: Resolved
Project: netvirt
Component/s: General
Affects Version/s: Carbon
Fix Version/s: None

Type: Bug Priority: Medium
Reporter: Itzik Brown Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Attachments: Text File karaf.log     Text File server.log    
External issue ID: 8961

 Description   

Description of problem:

An instance fails to start when it's attached with a previously port.

Version-Release number of selected component (if applicable):
python-networking-odl-11.0.0-0.20170721155128.a047729.el7ost.noarch
opendaylight-6.1.0-2.el7ost.noarch

How reproducible:

Steps to Reproduce:
1. Create a port
2. Launch an instance with the above port
3. Terminate the instance
4. Launch an instance with the above port
5. Verify that the instance is in 'spawning' state and then Error state

 Comments   
Comment by Itzik Brown [ 09/Aug/17 ]

Attachment server.log has been added with description: Neutron server log

Comment by Itzik Brown [ 09/Aug/17 ]

Attachment karaf.log has been added with description: Karaf log

Comment by Y Ananth [ 25/Aug/17 ]

I have tried to reproduce using steps given. I have observed that when I created second instance using the used port there is a little delay in getting the VM ip but it gets and it is is in running state.

I even created third VM instance for the same used port it also gets an ip after a bit delay and it is in running state.

Steps I have tried with Carbon SR1 and latest networking odl:

(openstack) network create l2_network_1 --provider-network-type vxlan

(openstack) subnet create --network l2_network_1 --subnet-range 10.0.0.0/24 l2_subnet_1

(openstack) port create --network l2_network_1 port1

(openstack) server create --image cirros --flavor cirros --nic port-id=port1 VM1 --security-group default

(openstack) console log show VM1

(openstack) server delete VM1

(openstack) server create --image cirros --flavor cirros --nic port-id=port1 VM2 --security-group default

(openstack) console log show VM2

(openstack) server delete VM2

It seems to be working fine. Can we close this bug.

Comment by Itzik Brown [ 27/Aug/17 ]

Still happens to me.

Comment by Y Ananth [ 28/Aug/17 ]

I'm using networking_odl-4.0.1.dev21 I think problem is related to version. Can you please guide me where to get the specific version where you observed issue.

Comment by Itzik Brown [ 17/Sep/17 ]

Hi,
I'm using stable/pike.

Itzik

Generated at Wed Feb 07 20:22:35 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.