get_panel_group error with enabled panel tests

[Matt Borland]

When enabling panels in patches such as:
- https://review.openstack.org/#/c/205296/ (which involves setting Disabled to False)

The feature works perfectly fine when viewed. However, an error comes up when the tests are run, in openstack_dashboard.test.test_plugins.panel_test.

The call to get_panel_group fails:
ERROR: test_remove_panel (openstack_dashboard.test.test_plugins.panel_tests.PanelPluginTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/mborland/horizon/openstack_dashboard/test/test_plugins/panel_tests.py", line 65, in test_remove_panel
    [p.__class__ for p in dashboard.get_panels()])
  File "/home/mborland/horizon/horizon/base.py", line 451, in get_panels
    panel_groups = self.get_panel_groups()
  File "/home/mborland/horizon/horizon/base.py", line 470, in get_panel_groups
    registered.pop(panel.__class__)
KeyError: <class 'openstack_dashboard.dashboards.admin.ngdefaults.panel.NgDefaults'>

When this happens, it seems the panel groups are not quite aligned with what is enabled.

[OpenStack Infra (hudson-openstack)]

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

[David Lyle (david-lyle)]

The problem is in the PanelPluginTests for testing plugin loading. The problem is we have a mixed model of how the dashboard and panels are loaded. Some panels are hardcoded into the dashboards. when you add new ones that aren't, they aren't picked up in this test, because it's specifying a different location for plugin files.

Since the addition is happening to the admin dashboard and not the project dashboard as with previous additions. We are seeing the error.

[David Lyle (david-lyle)]

I've just spent two days working on deeper fix for this bug. So took ownership. Hope you don't mind Matt :)

[Matt Borland (palecrow)]

Not at all..I appreciate you taking the time...let me know how I can help!

Matt

On Thursday, July 30, 2015, David Lyle <email address hidden> wrote:

> I've just spent two days working on deeper fix for this bug. So took
> ownership. Hope you don't mind Matt :)
>
>
> ** Changed in: horizon
> Assignee: Matt Borland (palecrow) => David Lyle (david-lyle)
>
> ** Changed in: horizon
> Status: In Progress => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1479018
>
> Title:
> get_panel_group error with enabled panel tests
>
> Status in OpenStack Dashboard (Horizon):
> Confirmed
>
> Bug description:
> When enabling panels in patches such as:
> - https://review.openstack.org/#/c/205296/ (which involves setting
> Disabled to False)
>
> The feature works perfectly fine when viewed. However, an error comes
> up when the tests are run, in
> openstack_dashboard.test.test_plugins.panel_test.
>
> The call to get_panel_group fails:
> ERROR: test_remove_panel
> (openstack_dashboard.test.test_plugins.panel_tests.PanelPluginTests)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
> File
> "/home/mborland/horizon/openstack_dashboard/test/test_plugins/panel_tests.py",
> line 65, in test_remove_panel
> [p.__class__ for p in dashboard.get_panels()])
> File "/home/mborland/horizon/horizon/base.py", line 451, in get_panels
> panel_groups = self.get_panel_groups()
> File "/home/mborland/horizon/horizon/base.py", line 470, in
> get_panel_groups
> registered.pop(panel.__class__)
> KeyError: <class
> 'openstack_dashboard.dashboards.admin.ngdefaults.panel.NgDefaults'>
>
>
> When this happens, it seems the panel groups are not quite aligned with
> what is enabled.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/horizon/+bug/1479018/+subscriptions
>

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/208643
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=8303782f1e67c00f3000acf12773a7df7581fc61
Submitter: Jenkins
Branch: master

commit 8303782f1e67c00f3000acf12773a7df7581fc61
Author: David Lyle <email address hidden>
Date: Mon Aug 3 14:23:42 2015 -0600

    Move Horizon to pure plugin loading only

    The root cause of 1479018 was the mixed method for loading content in
    horizon. This patch moves horizon to load purely from enabled files.
    There are a couple of things that were required to allow this change.

    1) Adding a mechanism, can_register() to horizon/base.py to handle the
    configuration based loading checks that had been accumulating in the
    panel.py files. This is an optional static method in Panel to
    encapsulate such configuration (read settings) based panel loading
    logic. And added testing for and documentation for this addition.

    2) Create a numbering scheme for plugins. Moved the base dashboards to
    _1000_project.py _2000_admin.py _3000_identity.py _5000_settings.py.
    then populated the required panel_group and panel enabled files sparsely
    in those ranges. The sparseness is to allow for future additions.
    Additionally, I moved the already added Angular based panels next to
    their Django counterparts.

    Once the configuration loading was normalized, the bug reported in
    1479018 was resolved and tests work with plugins panels in all
    dashboards.

    Close-Bug: #1479018
    Partially implements: blueprint plugin-sanity

    Change-Id: I657e7ce37b2593a901a859cebf3d6ff8ada91941

[OpenStack Infra (hudson-openstack)]

Change abandoned by Matt Borland (<email address hidden>) on branch: master
Review: https://review.openstack.org/206594
Reason: David Lyle came up with a better solution.