unable to retrieve the ports

Bug #1717893 reported by hyunsik Yang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Fix Released
Medium
Akihiro Motoki

Bug Description

Pike Master release,

When you click the compute --> Instance and try to Launch Instance, you can see the error message on the dashboard.

Error: Unable to retrieve the ports

https://review.openstack.org/#/c/504916/

Tags: neutron
Revision history for this message
hyunsik Yang (yangun) wrote :
Changed in horizon:
assignee: nobody → hyunsik Yang (yangun)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to horizon (master)

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

Changed in horizon:
status: New → In Progress
Revision history for this message
hyunsik Yang (yangun) wrote :

Fix proposed to branch : master
review : https://review.openstack.org/#/c/504916/

description: updated
Revision history for this message
hongbin (hongbin034) wrote :

Note: This bug affects zun-ui as well.

Revision history for this message
Gary W. Smith (gary-w-smith) wrote :

Although this appears to be a benign error, marking as medium since it is in such a highly used portion of the UI.

Changed in horizon:
importance: Undecided → Medium
Revision history for this message
Akihiro Motoki (amotoki) wrote :

I cannot reproduce this even after creating a port which can be attached to a new instance. I tried to reproduce this both with stable/pike branch and master branch (queens). Could you provide a way to reproduce this?

Revision history for this message
hyunsik Yang (yangun) wrote :

When you click the launch instance button in the compute, you can see that error.

Before pushing the button, you should make a network first.

please check it again.

Revision history for this message
Akihiro Motoki (amotoki) wrote :

I investigate the detail conditions to reproduce this more. What I see are:

- This bug always occurs when 'trunk' neutron extension is not enabled.
- This occurs only for the master branch (queens). This never happens for Pike. (so the original bug report "pike master" is incorrect)

As a fix, we should check the availability of 'trunk' extension and if it is not available we should fall-back into the previous behavior (without trunk port and subport handling). At least the attached patch in #1 is not the correct approach.

Revision history for this message
Akihiro Motoki (amotoki) wrote :

This means we cannot launch an instance when 'trunk' extension is not enabled in neutron, so I raises the priority to Critical.

tags: added: neutron
Changed in horizon:
importance: Medium → Critical
milestone: none → queens-1
Changed in horizon:
assignee: hyunsik Yang (yangun) → Akihiro Motoki (amotoki)
Revision history for this message
Akihiro Motoki (amotoki) wrote :

Changing the priority back to Medium as using 'neutron ports' is not a popular feature.

Changed in horizon:
importance: Critical → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to horizon (master)

Reviewed: https://review.openstack.org/504916
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=61ad9f69bde5180af195a254038ca8280a0ffbb9
Submitter: Jenkins
Branch: master

commit 61ad9f69bde5180af195a254038ca8280a0ffbb9
Author: Akihiro Motoki <email address hidden>
Date: Tue Sep 19 18:01:52 2017 +0000

    Fix a bug to unable to retrieve ports when no trunk ext

    When neutron trunk extension is not enabled, we cannot retrieve
    network ports for a new instance. The current version of
    port_list_with_trunk_types assumes the trunk extension is always
    available, so if it is not enabled we cannot retrieve network ports.
    This commit changes the logic to check whether the trunk extension
    is enabled and if not it does not retrieve trunk information.

    Change-Id: I2aa476790820f9512fe4728e0a806bd543021b0b
    Closes-Bug: #1717893

Changed in horizon:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/horizon 13.0.0.0b1

This issue was fixed in the openstack/horizon 13.0.0.0b1 development milestone.

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.