Port remains in status DOWN when fields "Device ID" and "Device owner" are filled from dashboard

Bug #1913038 reported by Jan Wasilewski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Expired
Undecided
Unassigned

Bug Description

Hi,

I would like to present scenario when port remains down even if full procedure is correct:

Test procedure:
- Go to horizon
- Go to Network-> Networks-> (select your network) -> Ports
- Click "Create port"
- Fill all fields: Name, Device ID, Device owner, MAC(that can be empty)
- Next, go to Compute -> Instances
- Select your instance and click "Attach interface"
- Select "by Port" and select your newly created port

Expected outcome:
Port is attached successfully and mark as active

Actual behaviour:
Port is down

That was tested against:
queens, rocky, stein releases

Screen attached which pools needs to be filled(provided here as XXX, but correct device id was provided there).

If something more is needed - please let me know.

Revision history for this message
Jan Wasilewski (janwasilewski) wrote :
Revision history for this message
Slawek Kaplonski (slaweq) wrote :

Hi,

Thx for reporting that bug. I have few more questions:

- Is VM in Active state and port still in DOWN?
- Is it the same when You start vm and nova will create port automatically for You?
- What neutron backend are You using?
- Can You provide us debug logs which contains moment when such port was created from the neutron server and neutron L2 agent?

Changed in neutron:
status: New → Incomplete
Revision history for this message
Jan Wasilewski (janwasilewski) wrote :

Hi,

answering to your questions:
1. VM is Active and port is still down.
2. No, that is working fine, only this procedure which I described is leading to such strange behaviour as I think it is a bug. If I will not provide Device ID, then everything is fine...really strange
3. I'm using linux bridges
4. Sure, please let me know which logs you need, I will provide it.

Best regards,
Jan

Revision history for this message
Rodolfo Alonso (rodolfo-alonso-hernandez) wrote :

Hello:

The Linux Bridge agent and the server logs, in debug mode, can be useful to debug this issue. Also Nova server logs can help, because this process is triggered by a Nova command.

I don't have a Linux Bridge environment, but I have an OVS one. I've tested this operation using Horizon and the command line and in both cases the port is attached correctly to the VM and the status is "ACTIVE".

Please, provide the Neutron and Nova logs, in debug mode, to see where the problem could be.

Regards.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for neutron because there has been no activity for 60 days.]

Changed in neutron:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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