After the vm's port name is modified, the port status changes from down to active.

[feixiang]

Hello,

I've faced a problem with ml2 plugin in Neutron (Queens).

steps as as follows:
1. stop VM A, The port status of VM A changes from active to down.

2. update the port name.

3. the port status will change from down to active.

Is this phenomenon correct?

[Brian Haley (brian-haley)]

Confirmed using openstackclient.

$ openstack port set --debug --name dev_server1 $id

(snippet from output shows only name in dict() passed to PUT, but status active in response)

REQ: curl -g -i -X PUT http://10.18.57.47:9696/v2.0/ports/f6c77196-41f2-4508-9c2f-8ee2d43f06ca -H "Content-Type: application/json" -H "User-Agent: openstacksdk/0.25.0 keystoneauth1/3.13.1 python-requests/2.21.0 CPython/2.7.15rc1" -H "X-Auth-Token: {SHA256}0e2dc7a61dbaed51728d9266c4cb8bb86bb4020df62fa636ffe95359ce842847" -d '{"port": {"name": "dev_server1"}}'
Manager RegionOne ran task network.PUT.ports in 0.00172185897827s
http://10.18.57.47:9696 "PUT /v2.0/ports/f6c77196-41f2-4508-9c2f-8ee2d43f06ca HTTP/1.1" 200 858
RESP: [200] Connection: keep-alive Content-Length: 858 Content-Type: application/json Date: Mon, 11 Mar 2019 19:19:39 GMT X-Openstack-Request-Id: req-4cab95b7-da09-4bc9-95d5-397a603d22cf
RESP BODY: {"port":{"status":"ACTIVE","created_at":"2019-03-11T19:18:55Z","description":"","allowed_address_pairs":[],"tags":[],"network_id":"b86c4ae3-997c-4c6b-b2fb-7c3c4a1ab0f6","tenant_id":"a0680cc922554cdea984c568c5461629","extra_dhcp_opts":[],"admin_state_up":true,"updated_at":"2019-03-11T19:19:38Z","name":"dev_server1","device_owner":"compute:nova","revision_number":5,"mac_address":"fa:16:3e:c2:63:23","binding:vnic_type":"normal","port_security_enabled":true,"project_id":"a0680cc922554cdea984c568c5461629","fixed_ips":[{"subnet_id":"4f87cab1-697d-48bf-b9e4-7d8c62a65655","ip_address":"10.0.0.45"},{"subnet_id":"0c3caf2e-83a2-4222-927d-e41e0f2a07ca","ip_address":"fd21:882e:c594:0:f816:3eff:fec2:6323"}],"id":"f6c77196-41f2-4508-9c2f-8ee2d43f06ca","security_groups":["bd6c3110-dc9a-4e3d-833f-062dd530a7d3"],"device_id":"37a1408b-27e0-4291-a011-28ddcf02ea4b"}}

[Brian Haley (brian-haley)]

I just tried to recreate this on the latest code in Antelope development and can't reproduce the issue. I could not find an obvious change that fixed it, but I'll close for now. Please re-open if you see it again.