yahoo-eng-team team mailing list archive

[Graham Lenton <maharg101@xxxxxxxxx>]

Public bug reported:

Instances not in the default availability zone (which is 'nova' by
default) are displayed incorrectly in the Network topology graph in
Horizon - as shown in the attached image.

If you drag the errant instance you can see it is actually rendered
outside the scope of the 'colour bubble', whereas instances in the
default availability zone are always kept within the 'colour bubble'
however much you attempt to drag them out.

Looking at
https://github.com/openstack/horizon/blame/master/openstack_dashboard/static/js/horizon.networktopology.js
it seems that checks are made against port.device_owner to see if it
matches the value 'compute:nova', but for instances in other
availability zones, the value is not 'compute:nova' but 'compute:name-
of-other-az'.

I think it would be sufficient to change the checks to be
port.device_owner.startsWith("compute:") but I have not yet been able to
test this.

This bug is present in all versions of Horizon since the 'curvature
topology' was introduced in Liberty in 2015.

** Affects: horizon
     Importance: Undecided
         Status: New


** Tags: horizon-core

** Attachment added: "Screen Shot 2019-03-15 at 09.47.39.png"
   https://bugs.launchpad.net/bugs/1820260/+attachment/5246415/+files/Screen%20Shot%202019-03-15%20at%2009.47.39.png

** Tags added: horizon

** Tags removed: horizon
** Tags added: horizon-core

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1820260

Title:
  Network topology graph incorrectly renders instances in non-default
  availability zone

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Instances not in the default availability zone (which is 'nova' by
  default) are displayed incorrectly in the Network topology graph in
  Horizon - as shown in the attached image.

  If you drag the errant instance you can see it is actually rendered
  outside the scope of the 'colour bubble', whereas instances in the
  default availability zone are always kept within the 'colour bubble'
  however much you attempt to drag them out.

  Looking at
  https://github.com/openstack/horizon/blame/master/openstack_dashboard/static/js/horizon.networktopology.js
  it seems that checks are made against port.device_owner to see if it
  matches the value 'compute:nova', but for instances in other
  availability zones, the value is not 'compute:nova' but 'compute:name-
  of-other-az'.

  I think it would be sufficient to change the checks to be
  port.device_owner.startsWith("compute:") but I have not yet been able
  to test this.

  This bug is present in all versions of Horizon since the 'curvature
  topology' was introduced in Liberty in 2015.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1820260/+subscriptions