[Yahoo-eng-team] [Bug 1647766] [NEW] sidebar doesn't show when network service not present
Public bug reported: In cases where the network service is not present, e.g. a Swift-only installation, it is possible that a call to list_extensions() will raise a ServiceCatalogException, which will cause the entire sidebar to fail to render. This means that the included in horizon/templates/horizon/common/_sidebar.html element is not present. ** Affects: horizon Importance: Undecided Assignee: Matt Borland (palecrow) Status: In Progress -- 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/1647766 Title: sidebar doesn't show when network service not present Status in OpenStack Dashboard (Horizon): In Progress Bug description: In cases where the network service is not present, e.g. a Swift-only installation, it is possible that a call to list_extensions() will raise a ServiceCatalogException, which will cause the entire sidebar to fail to render. This means that the included in horizon/templates/horizon/common/_sidebar.html element is not present. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1647766/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1628588] [NEW] Magic Search behavioral problems
Public bug reported: This bug covers a host of Magic Search behavioral problems: * text entry is borken when clicking to make a new facet * No ‘x’ icon when text search only * When text search, then click “x”, then text search NOT removed and search result not updated * When text search, then click facet, then text hidden but still used * When text search, then select a facet, hit main “x”, then only facet removed, text search NOT removed * When text search, enter to make text facet, then “x”, then select a “Type” “Image” facet, then the text facet reappears, then “x” again and Image facet cleared but text facet remains ** Affects: horizon Importance: Undecided Assignee: Matt Borland (palecrow) Status: In Progress ** Tags: newton-backport-potential ** Tags added: newton-backport-potential -- 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/1628588 Title: Magic Search behavioral problems Status in OpenStack Dashboard (Horizon): In Progress Bug description: This bug covers a host of Magic Search behavioral problems: * text entry is borken when clicking to make a new facet * No ‘x’ icon when text search only * When text search, then click “x”, then text search NOT removed and search result not updated * When text search, then click facet, then text hidden but still used * When text search, then select a facet, hit main “x”, then only facet removed, text search NOT removed * When text search, enter to make text facet, then “x”, then select a “Type” “Image” facet, then the text facet reappears, then “x” again and Image facet cleared but text facet remains To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1628588/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1609843] [NEW] LBaaS dashboard doesn't respect OPENSTACK_SSL settings
Public bug reported: The LBaaS dashboard doesn't respect the settings: OPENSTACK_SSL_NO_VERIFY OPENSTACK_SSL_CACERT This means that sessions aren't created properly for conditions where those are relevant. ** Affects: horizon Importance: Undecided Status: New -- 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/1609843 Title: LBaaS dashboard doesn't respect OPENSTACK_SSL settings Status in OpenStack Dashboard (Horizon): New Bug description: The LBaaS dashboard doesn't respect the settings: OPENSTACK_SSL_NO_VERIFY OPENSTACK_SSL_CACERT This means that sessions aren't created properly for conditions where those are relevant. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1609843/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1600352] [NEW] Launch Instance from NG Images fails on first attempt
Public bug reported: Consistently, Launch Instance from the Angnular Images panel fails on first attempt. This is because magic-search relies on elements being present that aren't always initialized right away. It's OK, the lifecycle will catch up, but at first we need to exclude rendering the magic-search when it's not ready. You can recreate this by enabling Angular Images panel: enabled via: ./openstack_dashboard/enabled/_1051_project_ng_images_panel.py Go to the panel, then with the JS console open, try to launch an instance from an image in its item actions. Notice a) how there are errors in the console and b) how there is Angular crud on many of the steps using magic-search. Apply the fix, and see how (a) and (b) are no longer present. ** Affects: horizon Importance: Undecided Status: New ** Description changed: - Consistently, Launch Instance from NG Images fails on first attempt. + Consistently, Launch Instance from the Angnular Images panel fails on + first attempt. This is because magic-search relies on elements being present that aren't always initialized right away. It's OK, the lifecycle will catch up, but at first we need to exclude rendering the magic-search when it's not ready. + + You can recreate this by enabling Angular Images panel: + + enabled via: + ./openstack_dashboard/enabled/_1051_project_ng_images_panel.py + + Go to the panel, then with the JS console open, try to launch an + instance from an image in its item actions. Notice a) how there are + errors in the console and b) how there is Angular crud on many of the + steps using magic-search. ** Description changed: Consistently, Launch Instance from the Angnular Images panel fails on first attempt. This is because magic-search relies on elements being present that aren't always initialized right away. It's OK, the lifecycle will catch up, but at first we need to exclude rendering the magic-search when it's not ready. You can recreate this by enabling Angular Images panel: enabled via: ./openstack_dashboard/enabled/_1051_project_ng_images_panel.py Go to the panel, then with the JS console open, try to launch an instance from an image in its item actions. Notice a) how there are errors in the console and b) how there is Angular crud on many of the steps using magic-search. + + Apply the fix, and see how (a) and (b) are no longer present. -- 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/1600352 Title: Launch Instance from NG Images fails on first attempt Status in OpenStack Dashboard (Horizon): New Bug description: Consistently, Launch Instance from the Angnular Images panel fails on first attempt. This is because magic-search relies on elements being present that aren't always initialized right away. It's OK, the lifecycle will catch up, but at first we need to exclude rendering the magic-search when it's not ready. You can recreate this by enabling Angular Images panel: enabled via: ./openstack_dashboard/enabled/_1051_project_ng_images_panel.py Go to the panel, then with the JS console open, try to launch an instance from an image in its item actions. Notice a) how there are errors in the console and b) how there is Angular crud on many of the steps using magic-search. Apply the fix, and see how (a) and (b) are no longer present. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1600352/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1432808] Re: variablize fonts
I believe this is now accounted for by the theming work. Diana, any thoughts on this? ** Changed in: horizon Status: New => Won't Fix -- 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/1432808 Title: variablize fonts Status in OpenStack Dashboard (Horizon): Won't Fix Bug description: In some cases fonts (family, size, etc) are specified as variables and other times they are in the components themselves. We should move to one consistent method. I propose variables. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1432808/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1597823] [NEW] Angular fall-through redirection doesn't use WEBROOT
Public bug reported: When on an Angular page and using the fall-through routing (routing from an Angular page back to a Django page using Angular relative paths), the redirect doesn't respect WEBROOT. This is best seen when using relative links in URLs, like in Searchlight panels and linking to internal pages, only when WEBROOT is other than '/'. ** Affects: horizon Importance: Undecided Status: New ** Tags: angularjs -- 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/1597823 Title: Angular fall-through redirection doesn't use WEBROOT Status in OpenStack Dashboard (Horizon): New Bug description: When on an Angular page and using the fall-through routing (routing from an Angular page back to a Django page using Angular relative paths), the redirect doesn't respect WEBROOT. This is best seen when using relative links in URLs, like in Searchlight panels and linking to internal pages, only when WEBROOT is other than '/'. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1597823/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1596560] [NEW] NG Image registers Create Image incorrectly
Public bug reported: NG Image registers its "Create Image" action as a batch action, when it should instead be a global action. The effect of this is somewhat small for typical Horizon, but it has effects in Searchlight or anywhere that quick-launch actions are to be presented. ** Affects: horizon Importance: Undecided Assignee: Matt Borland (palecrow) Status: In Progress -- 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/1596560 Title: NG Image registers Create Image incorrectly Status in OpenStack Dashboard (Horizon): In Progress Bug description: NG Image registers its "Create Image" action as a batch action, when it should instead be a global action. The effect of this is somewhat small for typical Horizon, but it has effects in Searchlight or anywhere that quick-launch actions are to be presented. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1596560/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1596061] [NEW] js linting is currently broken
Public bug reported: The JS linting has an error, but the infra job is not failing. We should at least fix the JS error. ** Affects: horizon Importance: Undecided Assignee: Matt Borland (palecrow) Status: In Progress -- 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/1596061 Title: js linting is currently broken Status in OpenStack Dashboard (Horizon): In Progress Bug description: The JS linting has an error, but the infra job is not failing. We should at least fix the JS error. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1596061/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1594466] [NEW] Additional params needed for openstack rc file
Public bug reported: There are some additional parameters needed for the openstack rc files, which are generated for download at: Access & Security > Download (appropriate) RC file. There are two kinds of files generated right now: Keystone v2 and Keystone v3. Which you see as options are based on your installation/configuration. Due to changes for Keystone v3, there are some new exports that should be honored: OS_INTERFACE OS_IDENTITY_API_VERSION OS_AUTH_VERSION They should be produced in both the v2 and v3 versions of the file for compatibility purposes. ** Affects: horizon Importance: Undecided Status: New -- 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/1594466 Title: Additional params needed for openstack rc file Status in OpenStack Dashboard (Horizon): New Bug description: There are some additional parameters needed for the openstack rc files, which are generated for download at: Access & Security > Download (appropriate) RC file. There are two kinds of files generated right now: Keystone v2 and Keystone v3. Which you see as options are based on your installation/configuration. Due to changes for Keystone v3, there are some new exports that should be honored: OS_INTERFACE OS_IDENTITY_API_VERSION OS_AUTH_VERSION They should be produced in both the v2 and v3 versions of the file for compatibility purposes. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1594466/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1593879] [NEW] hz-cell doesn't handle updates to data
Public bug reported: Unless you're using a template, hz-cell doesn't handle updates to data. This is because there is nothing to tell Angular that anything of value has changed. It's evaluated once and then done. To solve this, instead of using $scope.column, just pass the column in explicitly as a parameter. Angular will then know that it's valuable. You can see this in the implementation of Images (https://review.openstack.org/#/c/309561/); if you update "Protected" it is updated in the drawer but not in the table column. ** Affects: horizon Importance: Undecided Status: New ** Tags: angularjs ** Tags added: angularjs -- 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/1593879 Title: hz-cell doesn't handle updates to data Status in OpenStack Dashboard (Horizon): New Bug description: Unless you're using a template, hz-cell doesn't handle updates to data. This is because there is nothing to tell Angular that anything of value has changed. It's evaluated once and then done. To solve this, instead of using $scope.column, just pass the column in explicitly as a parameter. Angular will then know that it's valuable. You can see this in the implementation of Images (https://review.openstack.org/#/c/309561/); if you update "Protected" it is updated in the drawer but not in the table column. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1593879/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1299188] Re: qunit and jasmine urlpatterns should be defined only for test
Not going to fix this. Deployments shouldn't put tests in production, and regardless, you must expect some odd behavior if you place a production environment into DEBUG mode. This is also harmless behavior, so I'm not really worried about it. ** Changed in: horizon Status: New => Won't Fix -- 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/1299188 Title: qunit and jasmine urlpatterns should be defined only for test Status in OpenStack Dashboard (Horizon): Won't Fix Bug description: qunit and jasmine urlpatterns are defined in horizon/site_urls.py if settings.DEBUG is True. DEBUG=True is a valid situation without dev env (it is reasonable when testing). It is better to use another flag other than DEBUG and define url_pattern "jasmine" and "qunit" only if the new flag is True. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1299188/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1425049] Re: Pagination doesn't work for images by normal user
This was already fixed apparently. I notice Angular's Images table doesn't respect the limit, but that's a different way of paginating. ** Changed in: horizon Status: New => Fix Released -- 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/1425049 Title: Pagination doesn't work for images by normal user Status in OpenStack Dashboard (Horizon): Fix Released Bug description: The current pagination scheme using limit and marker doesn't work by normal user for images. Steps to Reproduce: 1. Set "Items Per Page" to 3 under "settings" using Horizon 2. Ensure that, you have more than 3 images 3. Log in by Normal user. 4. Click on Images It show all available images for that particular user on same page. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1425049/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1580357] Re: Launch Instance NG does not auto select default security group or default to selecting the only network in a Project
*** This bug is a duplicate of bug 1587681 *** https://bugs.launchpad.net/bugs/1587681 ** This bug has been marked a duplicate of bug 1587681 new launch instance wizard defaults -- 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/1580357 Title: Launch Instance NG does not auto select default security group or default to selecting the only network in a Project Status in OpenStack Dashboard (Horizon): New Bug description: In the Mitaka Release of Horizon, the Launch Instance NG panels do not select the 'default' security group and if there is only one network in a Project it does not default to that network. In the Launch Instance Legacy workflow, this defaulted to the 'default' security group and if you only had one network it defaulted to select that network. In Mitaka, the Launch Instance Legacy workflow no longer selects the 'default' security group since it is defaulting to using the string instead of the id of the 'default' network and this change broke that [0]. I'm not expecting the Launch Instance Legacy workflow to be fixed, just documenting that fact since I switched back to that workflow expecting it to work like the Kilo dashboard. [0]: https://github.com/openstack/horizon/commit/5562694 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1580357/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1592835] [NEW] hz-dynamic-table has empty div when no facets
Public bug reported: hz-dynamic-table displays a weird empty div when there are no facets and the user has clicked in the search area. ** Affects: horizon Importance: Undecided Status: New ** Tags: angularjs ** Tags added: angularjs -- 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/1592835 Title: hz-dynamic-table has empty div when no facets Status in OpenStack Dashboard (Horizon): New Bug description: hz-dynamic-table displays a weird empty div when there are no facets and the user has clicked in the search area. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1592835/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1592834] [NEW] hz-dynamic-table inline batch actions not aligned
Public bug reported: If you use hz-dynamic-table's batch actions inline with the search bar, it doesn't format them particularly well, placing them generally in the space given, not pushing them to the right. ** Affects: horizon Importance: Undecided Status: New ** Tags: angularjs ** Tags added: angularjs -- 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/1592834 Title: hz-dynamic-table inline batch actions not aligned Status in OpenStack Dashboard (Horizon): New Bug description: If you use hz-dynamic-table's batch actions inline with the search bar, it doesn't format them particularly well, placing them generally in the space given, not pushing them to the right. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1592834/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1592543] [NEW] Images registration is using old registration technique
Public bug reported: The Images module is using an experimental version of getResourceType() to register names instead of the .setNames() registry feature. ** Affects: horizon Importance: Undecided Assignee: Matt Borland (palecrow) Status: In Progress -- 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/1592543 Title: Images registration is using old registration technique Status in OpenStack Dashboard (Horizon): In Progress Bug description: The Images module is using an experimental version of getResourceType() to register names instead of the .setNames() registry feature. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1592543/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1445728] Re: [Launch Instance Fix] Scroll doesn't track with collapse expand transfer tables
I get that there's a small UX issue here, but I'm not sure we really want to add auto-scroll-to-the-thing-clicked-on as a feature. The browser's scroll bar continues to function well, and expands, allowing access to all content appropriately. Won't fix. ** Changed in: horizon Status: Confirmed => Won't Fix -- 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/1445728 Title: [Launch Instance Fix] Scroll doesn't track with collapse expand transfer tables Status in OpenStack Dashboard (Horizon): Won't Fix Bug description: When I collapse /expand a transfer table row, it often pushes most of the content out of the bottom of the page. The page doesn't scroll with it, make a very unpleasant experience when collapsing, expanding more than a couple rows. It would be better of the scroll tracked better with the collapse / expand. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1445728/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1588389] [NEW] Change JS coverage report dir to match CTI
Public bug reported: Krotscheck has pointed out that to follow the CTI definition, we should place all our JS coverage reports in ./cover. This means we need subdirs in there for 'horizon' and 'openstack_dashboard'. https://governance.openstack.org/reference/cti/javascript-cti.html #executing-tests-and-code-coverage ** Affects: horizon Importance: Undecided Status: New -- 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/1588389 Title: Change JS coverage report dir to match CTI Status in OpenStack Dashboard (Horizon): New Bug description: Krotscheck has pointed out that to follow the CTI definition, we should place all our JS coverage reports in ./cover. This means we need subdirs in there for 'horizon' and 'openstack_dashboard'. https://governance.openstack.org/reference/cti/javascript-cti.html #executing-tests-and-code-coverage To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1588389/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1588064] [NEW] secret_key.py doesn't warn when reverting to insecure key generation
Public bug reported: secret_key.py is used to generate a 64-bit key used by Django; however when it cannot find the 'SystemRandom' extension to the 'random' package it reverts to a generator that is, by documentation, not secure cryptographically. Witness: https://docs.python.org/2/library/random.html Reverting to the generator without leaving a warning is a hazard from a system security perspective. We should log at WARN that there is a possible security issue in the configuration. ** Affects: horizon Importance: Undecided Status: New -- 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/1588064 Title: secret_key.py doesn't warn when reverting to insecure key generation Status in OpenStack Dashboard (Horizon): New Bug description: secret_key.py is used to generate a 64-bit key used by Django; however when it cannot find the 'SystemRandom' extension to the 'random' package it reverts to a generator that is, by documentation, not secure cryptographically. Witness: https://docs.python.org/2/library/random.html Reverting to the generator without leaving a warning is a hazard from a system security perspective. We should log at WARN that there is a possible security issue in the configuration. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1588064/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1588039] [NEW] Security groups need to be created in non-English characters
Public bug reported: There are many localizations that do not use standard ASCII, and the code currently restricts individuals from creating Security Groups with names containing non-ASCII characters. You can see in https://review.openstack.org/#/c/54007/ and the associated launchpad tickets that the current validation was only loosening overly-restrictive validation; I believe we need to restrict them even less. Unless there are specific reasons that the names need to be ASCII, we should loosen this restriction. ** Affects: horizon Importance: Undecided Status: New -- 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/1588039 Title: Security groups need to be created in non-English characters Status in OpenStack Dashboard (Horizon): New Bug description: There are many localizations that do not use standard ASCII, and the code currently restricts individuals from creating Security Groups with names containing non-ASCII characters. You can see in https://review.openstack.org/#/c/54007/ and the associated launchpad tickets that the current validation was only loosening overly-restrictive validation; I believe we need to restrict them even less. Unless there are specific reasons that the names need to be ASCII, we should loosen this restriction. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1588039/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1587698] [NEW] Improve reliability of gate's npm-run-test
Public bug reported: The npm-run-test job in the gate has shown itself to be less reliable lately. In particular it tends to hang until the timeout, after successfully completing the tests. There have been similar failures in the past due to a variety of reasons. Most likely there's a memory problem with the reloading of modules over and over again in Chrome. One factor that had affected this was the loading of modules that were too 'high' in the hierarchy. For example, instead of using 'horizon.app.core.images' a test would just load 'horizon.app.core' which would load ALL dependent modules, then have to destroy them. Ideally we localize the tests loading only the modules needed. Other options for assisting with the tests would be to reduce the number of dependencies within app.core, such as moving resource registrations out since they are not really needed as part of the core registrations (where common features are placed, esp. APIs). This bug will remain in effect until npm-run-test appears to be fully stabilized. ** Affects: horizon Importance: Undecided Assignee: Matt Borland (palecrow) Status: In Progress -- 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/1587698 Title: Improve reliability of gate's npm-run-test Status in OpenStack Dashboard (Horizon): In Progress Bug description: The npm-run-test job in the gate has shown itself to be less reliable lately. In particular it tends to hang until the timeout, after successfully completing the tests. There have been similar failures in the past due to a variety of reasons. Most likely there's a memory problem with the reloading of modules over and over again in Chrome. One factor that had affected this was the loading of modules that were too 'high' in the hierarchy. For example, instead of using 'horizon.app.core.images' a test would just load 'horizon.app.core' which would load ALL dependent modules, then have to destroy them. Ideally we localize the tests loading only the modules needed. Other options for assisting with the tests would be to reduce the number of dependencies within app.core, such as moving resource registrations out since they are not really needed as part of the core registrations (where common features are placed, esp. APIs). This bug will remain in effect until npm-run-test appears to be fully stabilized. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1587698/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1584207] [NEW] Angular Edit Image buttons styled wrong
Public bug reported: If you compare the buttons in the Angular Edit Image versus the Create Image, you'll notice that the Edit Image buttons look odd. This is because they use the wrong element for styling (button instead of label). This may actually be more of a global styling problem, but for now we should just align the two to look nice. ** Affects: horizon Importance: Undecided Status: New ** Tags: angularjs ** Tags added: angularjs -- 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/1584207 Title: Angular Edit Image buttons styled wrong Status in OpenStack Dashboard (Horizon): New Bug description: If you compare the buttons in the Angular Edit Image versus the Create Image, you'll notice that the Edit Image buttons look odd. This is because they use the wrong element for styling (button instead of label). This may actually be more of a global styling problem, but for now we should just align the two to look nice. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1584207/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1583346] [NEW] eslint produces quote-prop warnings
Public bug reported:
eslint currently produces quote-prop warnings, that is complaining that:
{a: 'apple'}
should be
{'a': 'apple'}
On IRC we just decided that this warning is not something we want to
follow in Horizon.
** Affects: horizon
Importance: Undecided
Assignee: Matt Borland (palecrow)
Status: In Progress
--
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/1583346
Title:
eslint produces quote-prop warnings
Status in OpenStack Dashboard (Horizon):
In Progress
Bug description:
eslint currently produces quote-prop warnings, that is complaining
that:
{a: 'apple'}
should be
{'a': 'apple'}
On IRC we just decided that this warning is not something we want to
follow in Horizon.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1583346/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1582912] [NEW] Update package.json / npm package versions
Public bug reported: We should update the package.json to newer versions early in the cycle. ** Affects: horizon Importance: Undecided Assignee: Matt Borland (palecrow) Status: In Progress -- 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/1582912 Title: Update package.json / npm package versions Status in OpenStack Dashboard (Horizon): In Progress Bug description: We should update the package.json to newer versions early in the cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1582912/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1445224] Re: [Launch Instance Fix] Errors for required transfer tables not obvious
I think this bug is a fixed. We currently display item-level messages with tooltips when an item should not be selected. We also indicate stars where there are problems with steps. For example, select a source image and specify that we want 10 of them. You should see that the Details step gets the * notice and the Flavor step, if the selected option doesn't fit, gets one too, along with indications saying why the option is not valid. So I think this one never got closed. ** Changed in: horizon Status: Confirmed => Fix Released -- 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/1445224 Title: [Launch Instance Fix] Errors for required transfer tables not obvious Status in OpenStack Dashboard (Horizon): Fix Released Bug description: When a step in the wizard requires the user to allocate at least one item (image, flavor, etc), a warning icon appears on the step. There is not hover help for the warning icon, but even when switching to that step there is not a corresponding warning icon indicating where the error is. It should be more obvious which fields are required, especially for transfer tables. This should have UX input, because I have a few other concerns. Should a user really see warning icons for steps that have required fields, but haven't even been visited (e.g. in a form, you'd normally see if the field is $dirty before marking invalid with a warning). Should there be some other indicator? Early UX feedback had feedback for different icons. In legacy wizard, there is just an indicator that a tab (step) has a required fields. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1445224/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1433317] Re: [Launch Instance fix] Flavor table should be sorted by RAM
I was going to cancel this, but I notice the code was slightly wrong regarding the sorting. I am putting up a patch that fixes the sorting (in the Angular default). ** Changed in: horizon Status: Won't Fix => Confirmed -- 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/1433317 Title: [Launch Instance fix] Flavor table should be sorted by RAM Status in OpenStack Dashboard (Horizon): In Progress Bug description: by default To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1433317/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1433317] Re: [Launch Instance fix] Flavor table should be sorted by RAM
** Changed in: horizon Status: Confirmed => Won't Fix -- 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/1433317 Title: [Launch Instance fix] Flavor table should be sorted by RAM Status in OpenStack Dashboard (Horizon): Confirmed Bug description: by default To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1433317/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1508240] Re: Launch Instance Wizard: modified flag shows on config script load
I disagree with classification of this as a bug. The buffer is "modified" from the blank buffer that exists. It's just like typing in a script. The moment that script is uploaded, it has modified the buffer. Unless someone describes why this is a bug, I'm considering this Won't Fix. ** Changed in: horizon Status: Confirmed => Won't Fix -- 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/1508240 Title: Launch Instance Wizard: modified flag shows on config script load Status in OpenStack Dashboard (Horizon): Won't Fix Bug description: This is for the angular Launch Instance Wizard. When launching an instance, and uploading a configuration script, the 'Modified' indicator shows immediately. It should show after the uploaded script is modified. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1508240/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1582790] [NEW] Selecting first option in transfer table confuses styling
Public bug reported: If you go to the Launch Instance wizard and select the first available option, for example in Source, you'll see the table-striping styling gets messed up (if you have the striping patch). This is because the markup improperly lets the unshown details row be presented; this needs to be restricted similarly to the primary row. To test the problem, verify that the Source option stripes rows properly when nothing is selected. Then select the first option. See how the rows now are formatted similarly (not striped). ** Affects: horizon Importance: Undecided Status: New -- 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/1582790 Title: Selecting first option in transfer table confuses styling Status in OpenStack Dashboard (Horizon): New Bug description: If you go to the Launch Instance wizard and select the first available option, for example in Source, you'll see the table-striping styling gets messed up (if you have the striping patch). This is because the markup improperly lets the unshown details row be presented; this needs to be restricted similarly to the primary row. To test the problem, verify that the Source option stripes rows properly when nothing is selected. Then select the first option. See how the rows now are formatted similarly (not striped). To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1582790/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1582732] [NEW] Row formatting for Angular tables is wrong
Public bug reported: The table formatting for the Angular tables makes all lines the same color, where they are supposed to alternate colors. This was recently changed, and can be tested by going to the Angular Images panel. ** Affects: horizon Importance: Undecided Status: New -- 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/1582732 Title: Row formatting for Angular tables is wrong Status in OpenStack Dashboard (Horizon): New Bug description: The table formatting for the Angular tables makes all lines the same color, where they are supposed to alternate colors. This was recently changed, and can be tested by going to the Angular Images panel. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1582732/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1580206] [NEW] Canceling some Angular actions makes them unclickable
Public bug reported: If you go to certain Angular actions, such as Edit Image or Create Image, after you click on them all other uses of that action set become unclickable. This is known to be a problem for Create Image and Edit Image; not confirmed for any other actions (Create Volume, Launch, Delete all work OK). ** Affects: horizon Importance: Undecided Status: New -- 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/1580206 Title: Canceling some Angular actions makes them unclickable Status in OpenStack Dashboard (Horizon): New Bug description: If you go to certain Angular actions, such as Edit Image or Create Image, after you click on them all other uses of that action set become unclickable. This is known to be a problem for Create Image and Edit Image; not confirmed for any other actions (Create Volume, Launch, Delete all work OK). To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1580206/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1577909] [NEW] hz-dynamic-table has two magic-search bars
Public bug reported: The hz-dynamic-table directive's template has two magic-search bars, one correctly outside the table, the other incorrectly placed inside the table. The one inside the table should be removed. A proper implementation of the hz-dynamic-table directive using magic- search will illustrate the problem. ** Affects: horizon Importance: Undecided Assignee: Matt Borland (palecrow) Status: In Progress -- 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/1577909 Title: hz-dynamic-table has two magic-search bars Status in OpenStack Dashboard (Horizon): In Progress Bug description: The hz-dynamic-table directive's template has two magic-search bars, one correctly outside the table, the other incorrectly placed inside the table. The one inside the table should be removed. A proper implementation of the hz-dynamic-table directive using magic- search will illustrate the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1577909/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1291069] Re: Modifying flavor access list modifies the flavor info
Similar to https://bugs.launchpad.net/horizon/+bug/1311561, which Cindy designated as Won't Fix. I agree. ** Changed in: horizon Status: In Progress => Won't Fix -- 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/1291069 Title: Modifying flavor access list modifies the flavor info Status in OpenStack Dashboard (Horizon): Won't Fix Bug description: When the user modifies the flavor access list, the flavor is removed and created again even when the flavor information hasn't chance so there was no need to update the flavor information To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1291069/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1421017] Re: Flavor/image size checks are insufficient and untested
*** This bug is a duplicate of bug 1401101 *** https://bugs.launchpad.net/bugs/1401101 ** This bug has been marked a duplicate of bug 1401101 Nova launch instance from snapshot ignores --min-disk -- 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/1421017 Title: Flavor/image size checks are insufficient and untested Status in OpenStack Dashboard (Horizon): In Progress Bug description: When launching an instance, Horizon does some checks to ensure that the flavor the user has chosen is large enough to support the image they have chosen. Unfortunately: 1. These checks are broken. For disk size, they only check the `min_disk` property of the image, not the image size or virtual size; as a result, the image disk size is only checked in practice if the user has bothered to set the `min_disk` property. 2. The unit tests for the checks are broken. They modify local versions of the glance image data, but then run the tests by passing image IDs, which means that the original unmodified test images are used. The tests happen to pass, accidentally, but they don't test what we think they're testing. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1421017/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1414118] Re: Horizon shows stacktrace instead of 401: unauthorized
I think that the current behavior is appropriate; if for some reason we're calling getVolumes when the user doesn't have access, there should be some sort of stack trace on the server logs. The bug is more whether we should be checking something to help prevent that call from being made, not to change the getVolumes behavior. ** Changed in: horizon Status: New => Won't Fix -- 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/1414118 Title: Horizon shows stacktrace instead of 401: unauthorized Status in OpenStack Dashboard (Horizon): Won't Fix Bug description: In Icehouse if a user is unauthorized to access volumes, horizon shows a popup upon login as well as when accesing volumes. In Juno, horizon shows no warning upon login, and as one access volumes it shows a stacktrace. One way to reproduce it is to edit on the cinder host the /etc/cinder /api-paste.ini file, and in the "filter:authtoken" section configure an auth_host that is not keystone. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1414118/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1369876] Re: Missing HttpOnly Attribute in Session Cookie
Yeah, reference: https://docs.djangoproject.com/en/1.8/ref/settings
/#csrf-cookie-secure ; I'm pretty sure that is the preferred method of
dealing with cookie disclosure.
** Changed in: horizon
Status: Confirmed => Won't Fix
--
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/1369876
Title:
Missing HttpOnly Attribute in Session Cookie
Status in OpenStack Dashboard (Horizon):
Won't Fix
Bug description:
Affected URL: https://Ip_address/admin/
Entity: csrftoken (Cookie)
Risk: It is possible to steal or manipulate customer session and cookies,
which might be used to impersonate a legitimate user, allowing the hacker to
view or alter user records, and to perform transactions as that user.
Causes: The web application sets session cookies without the HttpOnly
attribute
Recommend Fix: Add the 'HttpOnly' attribute to all session cookies.
The Test Requests and Responses:
GET /admin/ HTTP/1.1
Host: 9.5.29.52
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101
Firefox/24.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Referer: https://9.5.29.52/
Cookie: csrftoken=JPjBiDp6Ex6YDw3sgfZPCTPUwWKZdZTm;
sessionid=oad3bpy15qm8ntml9wx604yr79cc6zpb
Connection: keep-alive
HTTP/1.1 200 OK
Date: Fri, 12 Sep 2014 07:52:50 GMT
Server: Apache
Vary: Accept-Language,Cookie,Accept-Encoding
X-Frame-Options: SAMEORIGIN
Content-Language: en
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
2014/9/12 504
Transfer-Encoding: chunked
Content-Type: text/html
Set-Cookie: csrftoken=silTP6ARbLvXohF6YYFLlWHce0KZkjPy; expires=Fri,
11-Sep-2015 07:52:52 GMT; Max-Age=31449600; Path=/; secure
Set-Cookie: sessionid=ygq094phgr6og471j6n0asq7x6q37j6n; httponly; Path=/;
secure
Usage Overview - Cloud Management Dashboard
/*
Added so that we can append Horizon scoped JS events to
the DOM load events without running in to the "horizon"
name-space not currently being defined since we load the
scripts at the bottom of the page.
*/
var addHorizonLoadEvent = function(func) {
var old_onload = window.onload;
if (typeof window.onload != 'function') {
window.onload = func;
} else {
window.onload = function() {
old_onload();
func();
}
}
}
Cloud Management Dashboard
admin
admin
Settings
2014/9/12 505
TOC
http://docs.openstack.org"; target="_new">Help
Sign Out
Project
Compute
Overview
Instances
Volumes
Images
Access &
Security
Network
Network
Topology
Networks
Routers
Orchestration
Stacks
...
...
...
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1369876/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1489619] Re: Selected item disappears in ng launch instance after changing source
2.5) Selected Image for Boot Source (above) :) ** Changed in: horizon Status: In Progress => Fix Released ** Changed in: horizon Assignee: Cindy Lu (clu-m) => (unassigned) -- 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/1489619 Title: Selected item disappears in ng launch instance after changing source Status in OpenStack Dashboard (Horizon): Fix Released Bug description: On the Select Source page of the angular Launch Instance wizard, if you move an item from the Available table into the Allocated table and then change the Boot Source, the selected item disappears. If you switch back to the previous boot source that item is no longer found in the Available table and does not seem to show up again until closing and re-opening the wizard. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1489619/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1559279] [NEW] Glance JS API getImage() is inefficient
Public bug reported: The Glance API JS has a getImage() function that calls '/api/glance/images/' + id, with no trailing slash. When this hits the API, it is redirected via a 301 to '/api/glance/images/' + id + '/' (with a trailing slash). This adds a second network communication and thus increases latency. If the API is just called with a trailing slash, the API responds directly with the result, which is a bit faster. You can verify the bug and fix by watching the server in dev mode when going to the Angular Image Detail page. You will see a 301 call immediately followed by another call with the trailing slash. You can see this in the JavaScript window as well. After applying the fix, you should no longer see the 301 result as there will be no call for the resource without the trailing slash. ** Affects: horizon Importance: Undecided Assignee: Matt Borland (palecrow) Status: In Progress -- 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/1559279 Title: Glance JS API getImage() is inefficient Status in OpenStack Dashboard (Horizon): In Progress Bug description: The Glance API JS has a getImage() function that calls '/api/glance/images/' + id, with no trailing slash. When this hits the API, it is redirected via a 301 to '/api/glance/images/' + id + '/' (with a trailing slash). This adds a second network communication and thus increases latency. If the API is just called with a trailing slash, the API responds directly with the result, which is a bit faster. You can verify the bug and fix by watching the server in dev mode when going to the Angular Image Detail page. You will see a 301 call immediately followed by another call with the trailing slash. You can see this in the JavaScript window as well. After applying the fix, you should no longer see the 301 result as there will be no call for the resource without the trailing slash. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1559279/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1558772] [NEW] Magic-Search shouldn't exist inside of table structure
Public bug reported: Currently, the way the Angular Magic-Search directive works, it requires being placed in the context of a smart-table. This is not ideal and causes trouble with formatting. A good solution would allow the search bar directive to be placed outside of the table structure in the markup. ** Affects: horizon Importance: Undecided Status: New -- 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/1558772 Title: Magic-Search shouldn't exist inside of table structure Status in OpenStack Dashboard (Horizon): New Bug description: Currently, the way the Angular Magic-Search directive works, it requires being placed in the context of a smart-table. This is not ideal and causes trouble with formatting. A good solution would allow the search bar directive to be placed outside of the table structure in the markup. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1558772/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1559105] [NEW] Launching Instance from Volumes tabs fails
Public bug reported: When going to Volumes > Volumes (tab) or Volumes > Volume Snapshots, then choosing to Launch as Instance, if you wait about 10 seconds (enough for a background refresh, if there is an active refresh going on), the Launch Instance modal that was created will fail with the Javascript errors: "Error: [ngTransclude:orphan]..." It's possible this behavior only happens when one of the tabs is polling, which in my case I have a continuously deleting volume. Visually it will appear as though every several seconds another "layer" of Launch Instance modals are being added. ** Affects: horizon Importance: Undecided Status: New ** Description changed: When going to Volumes > Volumes (tab) or Volumes > Volume Snapshots, then choosing to Launch as Instance, if you wait about 10 seconds (enough for a background refresh, if there is an active refresh going on), the Launch Instance modal that was created will fail with the Javascript errors: "Error: [ngTransclude:orphan]..." It's possible this behavior only happens when one of the tabs is polling, which in my case I have a continuously deleting volume. + + Visually it will appear as though every several seconds another "layer" + of Launch Instance modals are being added. -- 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/1559105 Title: Launching Instance from Volumes tabs fails Status in OpenStack Dashboard (Horizon): New Bug description: When going to Volumes > Volumes (tab) or Volumes > Volume Snapshots, then choosing to Launch as Instance, if you wait about 10 seconds (enough for a background refresh, if there is an active refresh going on), the Launch Instance modal that was created will fail with the Javascript errors: "Error: [ngTransclude:orphan]..." It's possible this behavior only happens when one of the tabs is polling, which in my case I have a continuously deleting volume. Visually it will appear as though every several seconds another "layer" of Launch Instance modals are being added. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1559105/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1536681] [NEW] launch instance cannot use location provider
Public bug reported: The introduction of the location provider service in Angular doesn't check whether the page has a base tag before assuming html5 location management. This is not a relevant need for modals like the Launch Instance, which are not necessarily launched from an 'Angular page.' They typically perform standard routing without regard to html5 routing. Right now the establishment of the location provider breaks when used on a 'normal' page. ** Affects: horizon Importance: Undecided Status: New -- 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/1536681 Title: launch instance cannot use location provider Status in OpenStack Dashboard (Horizon): New Bug description: The introduction of the location provider service in Angular doesn't check whether the page has a base tag before assuming html5 location management. This is not a relevant need for modals like the Launch Instance, which are not necessarily launched from an 'Angular page.' They typically perform standard routing without regard to html5 routing. Right now the establishment of the location provider breaks when used on a 'normal' page. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1536681/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1535779] [NEW] Unnecessary image module in Angular
Public bug reported:
Unless I'm misunderstanding something, it appears that the items in the
path:
./openstack_dashboard/dashboards/project/static/dashboard/project/images/
are unnecessary/vestigial. It seems all such image-related features
should be in:
./openstack_dashboard/static/app/core/images/
The module that is currently in that unused directory specifies:
"horizon.dashboard.project.images" as its namespace; this shows itself
to be outdated as "horizon.app.core.images" is the proper namespace.
There are other items in a similar directory (.../dahsboard/project/)
that seem equally wrongly placed, but because that includes actual used
items, there may be more upheaval in moving, whereas there seem to be no
image-based features using "horizon.dashboard.project.images" ( find
openstack_dashboard/ -name "*.js" -exec grep -l
horizon.dashboard.project.images {} \; ).
** Affects: horizon
Importance: Undecided
Assignee: Matt Borland (palecrow)
Status: In Progress
--
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/1535779
Title:
Unnecessary image module in Angular
Status in OpenStack Dashboard (Horizon):
In Progress
Bug description:
Unless I'm misunderstanding something, it appears that the items in
the path:
./openstack_dashboard/dashboards/project/static/dashboard/project/images/
are unnecessary/vestigial. It seems all such image-related features
should be in:
./openstack_dashboard/static/app/core/images/
The module that is currently in that unused directory specifies:
"horizon.dashboard.project.images" as its namespace; this shows itself
to be outdated as "horizon.app.core.images" is the proper namespace.
There are other items in a similar directory (.../dahsboard/project/)
that seem equally wrongly placed, but because that includes actual
used items, there may be more upheaval in moving, whereas there seem
to be no image-based features using "horizon.dashboard.project.images"
( find openstack_dashboard/ -name "*.js" -exec grep -l
horizon.dashboard.project.images {} \; ).
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1535779/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1531982] [NEW] actions.py references missing/wrong template
Public bug reported: horizon/tables/actions.py seems to reference horizon/common/_data_table_table_action.html, which doesn't exist. This can be demonstrated when deleting multiple Instances (as an example). There will be a 500 error returned by a call to http://localhost:8000/project/instances/?action=launch&table=instances if one watches the requests. ** Affects: horizon Importance: Undecided Assignee: Matt Borland (palecrow) Status: New ** Changed in: horizon Assignee: (unassigned) => Matt Borland (palecrow) -- 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/1531982 Title: actions.py references missing/wrong template Status in OpenStack Dashboard (Horizon): New Bug description: horizon/tables/actions.py seems to reference horizon/common/_data_table_table_action.html, which doesn't exist. This can be demonstrated when deleting multiple Instances (as an example). There will be a 500 error returned by a call to http://localhost:8000/project/instances/?action=launch&table=instances if one watches the requests. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1531982/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1507703] [NEW] Karma for OSD doesn't load templates
Public bug reported: The openstack_dashboard Karma configuration is not looking in the right place for templates and other resources. For example, you cannot use the 'templates' module to load templates for use in directive testing. ** Affects: horizon Importance: Undecided Assignee: Matt Borland (palecrow) Status: In Progress -- 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/1507703 Title: Karma for OSD doesn't load templates Status in OpenStack Dashboard (Horizon): In Progress Bug description: The openstack_dashboard Karma configuration is not looking in the right place for templates and other resources. For example, you cannot use the 'templates' module to load templates for use in directive testing. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1507703/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1506942] [NEW] JS unit test statement coverage is low
Public bug reported: The JS unit test statement coverage in the ./horizon project has a threshold of 68%...way too low. There are a few places where coverage is particularly bad that should be given more tests. ** Affects: horizon Importance: Undecided Status: New -- 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/1506942 Title: JS unit test statement coverage is low Status in OpenStack Dashboard (Horizon): New Bug description: The JS unit test statement coverage in the ./horizon project has a threshold of 68%...way too low. There are a few places where coverage is particularly bad that should be given more tests. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1506942/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1506891] [NEW] JS Unit Test Branch Coverage is Low
Public bug reported: The JS unit test branch coverage is within 0.25% of its threshold, meaning slight variations may cause patches to trigger coverage failures. There are a few places where coverage is particularly bad that should be given more tests. ** Affects: horizon Importance: Undecided Status: New -- 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/1506891 Title: JS Unit Test Branch Coverage is Low Status in OpenStack Dashboard (Horizon): New Bug description: The JS unit test branch coverage is within 0.25% of its threshold, meaning slight variations may cause patches to trigger coverage failures. There are a few places where coverage is particularly bad that should be given more tests. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1506891/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1492265] [NEW] NG Launch Instance fails unlimited instance quota
Public bug reported: The Angular Launch Instance wizard fails to operate if the instance quota is unlimited (set to -1). This is largely due to logic that assumes a value greater than zero. ** Affects: horizon Importance: Undecided Status: New -- 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/1492265 Title: NG Launch Instance fails unlimited instance quota Status in OpenStack Dashboard (Horizon): New Bug description: The Angular Launch Instance wizard fails to operate if the instance quota is unlimited (set to -1). This is largely due to logic that assumes a value greater than zero. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1492265/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1484193] [NEW] Angular table pagination needs better verbiage
Public bug reported: The Angular table pagination currently says: "Showing 10 items" It would be more useful if it said something like: "Showing 10 of 25 items." (it doesn't need to say which page it's on as that is visually demonstrated in the nav bar.) ** Affects: horizon Importance: Undecided Status: New -- 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/1484193 Title: Angular table pagination needs better verbiage Status in OpenStack Dashboard (Horizon): New Bug description: The Angular table pagination currently says: "Showing 10 items" It would be more useful if it said something like: "Showing 10 of 25 items." (it doesn't need to say which page it's on as that is visually demonstrated in the nav bar.) To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1484193/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1479018] [NEW] get_panel_group error with enabled panel tests
Public bug reported: 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: When this happens, it seems the panel groups are not quite aligned with what is enabled. ** Affects: horizon Importance: Undecided Assignee: Matt Borland (palecrow) Status: In Progress -- 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/1479018 Title: get_panel_group error with enabled panel tests Status in OpenStack Dashboard (Horizon): In Progress 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: 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 -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1470982] [NEW] Corrections to WEBROOT docs
Public bug reported: There are a couple of minor typos and oversights in the WEBROOT documentation in the Settings page. 1) Misspelling of 'dashboard' 2) Exclusion of WSGIScriptAlias instruction for Apache 3) Inclusion of reminder to use collectstatic/compress after changing _variables.css ** Affects: horizon Importance: Undecided Status: New -- 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/1470982 Title: Corrections to WEBROOT docs Status in OpenStack Dashboard (Horizon): New Bug description: There are a couple of minor typos and oversights in the WEBROOT documentation in the Settings page. 1) Misspelling of 'dashboard' 2) Exclusion of WSGIScriptAlias instruction for Apache 3) Inclusion of reminder to use collectstatic/compress after changing _variables.css To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1470982/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1470645] [NEW] test_flavor_create is failing
Public bug reported: It seems that the test: gate-horizon-dsvm-integration: TestFlavor/test_flavor_create is failing frequently, on a timeout issue (see below). I verified that the function works manually, so the test is somehow failing incorrectly, either due to a short timeout, or some other mechanism. Any great ideas on how to fix this? a) short timeout: prolong timeout b) bad mechanism: fix mechanism c) unknown: skip test so people can get jobs through 2015-07-01 20:05:35.582 | 2015-07-01 20:05:35.434 | Traceback (most recent call last): 2015-07-01 20:05:35.582 | 2015-07-01 20:05:35.435 | File "/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/tests/test_flavors.py", line 31, in test_flavor_create 2015-07-01 20:05:35.583 | 2015-07-01 20:05:35.436 | swap_disk=0) 2015-07-01 20:05:35.583 | 2015-07-01 20:05:35.437 | File "/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/pages/admin/system/flavorspage.py", line 75, in create_flavor 2015-07-01 20:05:35.583 | 2015-07-01 20:05:35.439 | self._wait_till_spinner_disappears() 2015-07-01 20:05:35.583 | 2015-07-01 20:05:35.440 | File "/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/pages/basepage.py", line 70, in _wait_till_spinner_disappears 2015-07-01 20:05:35.584 | 2015-07-01 20:05:35.442 | self._wait_till_element_disappears(spinner) 2015-07-01 20:05:35.584 | 2015-07-01 20:05:35.443 | File "/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/basewebobject.py", line 96, in _wait_till_element_disappears 2015-07-01 20:05:35.584 | 2015-07-01 20:05:35.444 | timeout) 2015-07-01 20:05:35.584 | 2015-07-01 20:05:35.445 | File "/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/basewebobject.py", line 84, in _wait_until 2015-07-01 20:05:35.585 | 2015-07-01 20:05:35.447 | predicate) 2015-07-01 20:05:35.585 | 2015-07-01 20:05:35.448 | File "/opt/stack/new/horizon/.tox/py27integration/local/lib/python2.7/site-packages/selenium/webdriver/support/wait.py", line 78, in until 2015-07-01 20:05:35.585 | 2015-07-01 20:05:35.449 | raise TimeoutException(message, screen, stacktrace) 2015-07-01 20:05:35.585 | 2015-07-01 20:05:35.451 | selenium.common.exceptions.TimeoutException: Message: ** Affects: horizon Importance: Undecided Status: New ** Description changed: It seems that the test: - TestFlavor/test_flavor_create + gate-horizon-dsvm-integration: + TestFlavor/test_flavor_create is failing frequently, on a timeout issue (see below). I verified that the function works manually, so the test is somehow failing incorrectly, either due to a short timeout, or some other mechanism. Any great ideas on how to fix this? a) short timeout: prolong timeout b) bad mechanism: fix mechanism c) unknown: skip test so people can get jobs through 2015-07-01 20:05:35.582 | 2015-07-01 20:05:35.434 | Traceback (most recent call last): 2015-07-01 20:05:35.582 | 2015-07-01 20:05:35.435 | File "/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/tests/test_flavors.py", line 31, in test_flavor_create 2015-07-01 20:05:35.583 | 2015-07-01 20:05:35.436 | swap_disk=0) 2015-07-01 20:05:35.583 | 2015-07-01 20:05:35.437 | File "/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/pages/admin/system/flavorspage.py", line 75, in create_flavor 2015-07-01 20:05:35.583 | 2015-07-01 20:05:35.439 | self._wait_till_spinner_disappears() 2015-07-01 20:05:35.583 | 2015-07-01 20:05:35.440 | File "/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/pages/basepage.py", line 70, in _wait_till_spinner_disappears 2015-07-01 20:05:35.584 | 2015-07-01 20:05:35.442 | self._wait_till_element_disappears(spinner) 2015-07-01 20:05:35.584 | 2015-07-01 20:05:35.443 | File "/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/basewebobject.py", line 96, in _wait_till_element_disappears 2015-07-01 20:05:35.584 | 2015-07-01 20:05:35.444 | timeout) 2015-07-01 20:05:35.584 | 2015-07-01 20:05:35.445 | File "/opt/stack/new/horizon/openstack_dashboard/test/integration_tests/basewebobject.py", line 84, in _wait_until 2015-07-01 20:05:35.585 | 2015-07-01 20:05:35.447 | predicate) 2015-07-01 20:05:35.585 | 2015-07-01 20:05:35.448 | File "/opt/stack/new/horizon/.tox/py27integration/local/lib/python2.7/site-packages/selenium/webdriver/support/wait.py", line 78, in until 2015-07-01 20:05:35.585 | 2015-07-01 20:05:35.449 | raise TimeoutException(message, screen, stacktrace) 2015-07-01 20:05:35.585 | 2015-07-01 20:05:35.451 | selenium.common.exceptions.TimeoutException: Message: -- 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/1470645 Title: test_flavor_create is failing Status in OpenStack Dashboard (H
[Yahoo-eng-team] [Bug 1470592] Re: metadata widget tests failing
Caching problem on my browser, seemingly. ** Changed in: horizon Status: New => Invalid -- 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/1470592 Title: metadata widget tests failing Status in OpenStack Dashboard (Horizon): Invalid Bug description: Running the Jasmine tests: ./run_tests.sh --runserver http://:/jasmine Shows failures. These seem to be the result of changes in: https://review.openstack.org/#/c/173359/ To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1470592/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1470592] [NEW] metadata widget tests failing
Public bug reported: Running the Jasmine tests: ./run_tests.sh --runserver http://:/jasmine Shows failures. These seem to be the result of changes in: https://review.openstack.org/#/c/173359/ ** Affects: horizon Importance: Undecided Status: New -- 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/1470592 Title: metadata widget tests failing Status in OpenStack Dashboard (Horizon): New Bug description: Running the Jasmine tests: ./run_tests.sh --runserver http://:/jasmine Shows failures. These seem to be the result of changes in: https://review.openstack.org/#/c/173359/ To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1470592/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1455126] [NEW] Launch Instance (NG) network needs to use controller-as
Public bug reported: As suggested by: https://github.com/johnpapa/angular-styleguide#style-y030 The Launch Instance network-step controller should use 'controller-as' syntax. ** Affects: horizon Importance: Undecided Status: New -- 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/1455126 Title: Launch Instance (NG) network needs to use controller-as Status in OpenStack Dashboard (Horizon): New Bug description: As suggested by: https://github.com/johnpapa/angular-styleguide#style-y030 The Launch Instance network-step controller should use 'controller-as' syntax. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1455126/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1454804] [NEW] Dashboard jasmine_tests.py file is unnecessary
Public bug reported: openstack_dashboard/test/jasmine/jasmine_tests.py is unnecessary as the JS source, spec, and template files are all specified in the _10_project.py file. The file may be completely removed. ** Affects: horizon Importance: Undecided Assignee: Matt Borland (palecrow) Status: In Progress -- 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/1454804 Title: Dashboard jasmine_tests.py file is unnecessary Status in OpenStack Dashboard (Horizon): In Progress Bug description: openstack_dashboard/test/jasmine/jasmine_tests.py is unnecessary as the JS source, spec, and template files are all specified in the _10_project.py file. The file may be completely removed. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1454804/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1454395] [NEW] rickshaw.css and datepicker3.css getting 404s
Public bug reported: On many/most requests, rickshaw.css and datepicker3.css are trying to be fetched, but are not available (return a 404). paths requested: /horizon/lib/bootstrap_datepicker/datepicker3.css /horizon/lib/rickshaw.css ** Affects: horizon Importance: Undecided Status: New -- 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/1454395 Title: rickshaw.css and datepicker3.css getting 404s Status in OpenStack Dashboard (Horizon): New Bug description: On many/most requests, rickshaw.css and datepicker3.css are trying to be fetched, but are not available (return a 404). paths requested: /horizon/lib/bootstrap_datepicker/datepicker3.css /horizon/lib/rickshaw.css To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1454395/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1453858] [NEW] Fix existing JSCS errors
Public bug reported: When running ./run_tests.sh --jscs there are a few errors (trailing whitespace). These should be cleaned up. ** Affects: horizon Importance: Undecided Assignee: Matt Borland (palecrow) Status: In Progress ** Changed in: horizon Assignee: (unassigned) => Matt Borland (palecrow) -- 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/1453858 Title: Fix existing JSCS errors Status in OpenStack Dashboard (Horizon): In Progress Bug description: When running ./run_tests.sh --jscs there are a few errors (trailing whitespace). These should be cleaned up. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1453858/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1450799] [NEW] JSCS does not default param in run_tests.sh
Public bug reported: JSCS doesn't default its variable in run_tests.sh, which means that when ./run_tests.sh is run without the --jscs option, a warning message appears. ** Affects: horizon Importance: Undecided Status: New -- 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/1450799 Title: JSCS does not default param in run_tests.sh Status in OpenStack Dashboard (Horizon): New Bug description: JSCS doesn't default its variable in run_tests.sh, which means that when ./run_tests.sh is run without the --jscs option, a warning message appears. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1450799/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1450629] [NEW] Ensure that JS files follow JSCS rules
Public bug reported: Some JS files do not follow the established JSCS ruleset. Modify files so no notices are thrown. ** Affects: horizon Importance: Undecided Assignee: Matt Borland (palecrow) Status: In Progress -- 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/1450629 Title: Ensure that JS files follow JSCS rules Status in OpenStack Dashboard (Horizon): In Progress Bug description: Some JS files do not follow the established JSCS ruleset. Modify files so no notices are thrown. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1450629/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1450626] [NEW] No JavaScript code style checker
Public bug reported: There is currently no JavaScript code style checker in the development environment. JSCS is one typical code style checker that provides many good ways to establish formal rules. Ideally, we establish a patch with some basics, then add onto it as appropriate. ** Affects: horizon Importance: Undecided Assignee: Matt Borland (palecrow) Status: In Progress -- 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/1450626 Title: No JavaScript code style checker Status in OpenStack Dashboard (Horizon): In Progress Bug description: There is currently no JavaScript code style checker in the development environment. JSCS is one typical code style checker that provides many good ways to establish formal rules. Ideally, we establish a patch with some basics, then add onto it as appropriate. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1450626/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1449648] [NEW] Keystone API JS Service uses wrong method
Public bug reported: The KeystoneAPI service (in JS) has a grantRole function that uses the wrong method (delete instead of put) to grant the role. ** Affects: horizon Importance: Undecided Assignee: Matt Borland (palecrow) Status: In Progress ** Changed in: horizon Assignee: (unassigned) => Matt Borland (palecrow) -- 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/1449648 Title: Keystone API JS Service uses wrong method Status in OpenStack Dashboard (Horizon): In Progress Bug description: The KeystoneAPI service (in JS) has a grantRole function that uses the wrong method (delete instead of put) to grant the role. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1449648/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1446739] [NEW] Angular code should not reference global gettext
Public bug reported: Currently Django provides a window-global function gettext() (among others) that is used for presenting translated text. This mechanism is still needed, but it currently is not presented as a service (/factory). This means that the Angular code expects gettext() to be on the global scope, which is not only a bad practice but interferes with testing (having to supply a global-scope mechanism). The solution is to create a service (through a factory probably) that provides a function through injection. The rollout of this may be done in phases: - Create factory and example - Continue to expand use throughout existing code base - In some contexts, may actually delete the gettext reference from the global scope ** Affects: horizon Importance: Undecided Status: New -- 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/1446739 Title: Angular code should not reference global gettext Status in OpenStack Dashboard (Horizon): New Bug description: Currently Django provides a window-global function gettext() (among others) that is used for presenting translated text. This mechanism is still needed, but it currently is not presented as a service (/factory). This means that the Angular code expects gettext() to be on the global scope, which is not only a bad practice but interferes with testing (having to supply a global-scope mechanism). The solution is to create a service (through a factory probably) that provides a function through injection. The rollout of this may be done in phases: - Create factory and example - Continue to expand use throughout existing code base - In some contexts, may actually delete the gettext reference from the global scope To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1446739/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1440096] [NEW] Rename Util spec file to align with convention
Public bug reported: The spec (test) file: horizon/static/horizon/tests/jasmine/utilsSpec.js should be named to match the format '*.spec.js' like other such files. This makes it easier to differentiate from source code in wildcard searches, etc. ** Affects: horizon Importance: Undecided Assignee: Matt Borland (palecrow) Status: In Progress -- 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/1440096 Title: Rename Util spec file to align with convention Status in OpenStack Dashboard (Horizon): In Progress Bug description: The spec (test) file: horizon/static/horizon/tests/jasmine/utilsSpec.js should be named to match the format '*.spec.js' like other such files. This makes it easier to differentiate from source code in wildcard searches, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1440096/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1439794] [NEW] Fix several logical bugs in simpleModalService
Public bug reported: There are several logical bugs with the simple modal service: 1) There seems to be a 'cancel' option to pass to the service; it doesn't seem to be respected. 2) There are defaults for body and title that logically can never be used. 3) If not given appropriate parameters, it doesn't return an object and thus will fail oddly. ** Affects: horizon Importance: Undecided Assignee: Matt Borland (palecrow) Status: New ** Changed in: horizon Assignee: (unassigned) => Matt Borland (palecrow) ** Description changed: There are several logical bugs with the simple modal service: - 1) There seems to be a 'cancel' option to pass to the service; it doesn't seem to be respected. - 2) There are defaults for body and title that logically can never be used. - 3) If not given appropriate parameters, it doesn't return an object and thus will fail oddly. + 1) There seems to be a 'cancel' option to pass to the service; it doesn't seem to be respected. + 2) There are defaults for body and title that logically can never be used. + 3) If not given appropriate parameters, it doesn't return an object and thus will fail oddly. ** Description changed: There are several logical bugs with the simple modal service: - 1) There seems to be a 'cancel' option to pass to the service; it doesn't seem to be respected. + 1) There seems to be a 'cancel' option to pass to the service; it doesn't seem to be respected. 2) There are defaults for body and title that logically can never be used. 3) If not given appropriate parameters, it doesn't return an object and thus will fail oddly. -- 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/1439794 Title: Fix several logical bugs in simpleModalService Status in OpenStack Dashboard (Horizon): New Bug description: There are several logical bugs with the simple modal service: 1) There seems to be a 'cancel' option to pass to the service; it doesn't seem to be respected. 2) There are defaults for body and title that logically can never be used. 3) If not given appropriate parameters, it doesn't return an object and thus will fail oddly. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1439794/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1435869] [NEW] [Launch Instance Fix] Establish Baseline Unit Tests
Public bug reported: The Angular work done for Launch Instance should have a baseline set of unit tests for each of the steps and the infrastructure supporting them (model, wizard implementation, etc.). These tests should ensure that each component has basic tests in their associated .spec.js files. The expectations for such components would be: Controllers: - test for name - test injected elements (maybe inherent in other tests) - test each exposed logic function (whether on scope or on controller object) Filters: - should be tested for expected object - should be tested for lack of expected object (undefined, null, etc. preferably using angular's presence functions) ** Affects: horizon Importance: Undecided Status: New -- 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/1435869 Title: [Launch Instance Fix] Establish Baseline Unit Tests Status in OpenStack Dashboard (Horizon): New Bug description: The Angular work done for Launch Instance should have a baseline set of unit tests for each of the steps and the infrastructure supporting them (model, wizard implementation, etc.). These tests should ensure that each component has basic tests in their associated .spec.js files. The expectations for such components would be: Controllers: - test for name - test injected elements (maybe inherent in other tests) - test each exposed logic function (whether on scope or on controller object) Filters: - should be tested for expected object - should be tested for lack of expected object (undefined, null, etc. preferably using angular's presence functions) To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1435869/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1434221] [NEW] [Launch Instance Fix] Launch instance doesn't refresh instance tables
Public bug reported: On a successful launch instance wizard completion, the instance tables list doesn't refresh. Modify so the page reloads appropriately. ** Affects: horizon Importance: Undecided Status: New -- 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/1434221 Title: [Launch Instance Fix] Launch instance doesn't refresh instance tables Status in OpenStack Dashboard (Horizon): New Bug description: On a successful launch instance wizard completion, the instance tables list doesn't refresh. Modify so the page reloads appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1434221/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1434185] [NEW] [Launch Instance Fix] Launching from image doesn't default
Public bug reported: When launching the angular launch-instance wizard from an image table/detail, the image is not selected in the allocated section. ** Affects: horizon Importance: Undecided Status: New -- 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/1434185 Title: [Launch Instance Fix] Launching from image doesn't default Status in OpenStack Dashboard (Horizon): New Bug description: When launching the angular launch-instance wizard from an image table/detail, the image is not selected in the allocated section. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1434185/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1433113] [NEW] [Launch Instance Fix] Launch wizard from Image pages
Public bug reported: The new Launch-Instance wizard is not launched from the Image table or detail screens. The old mechanism needs to be replaced with the new, carrying the original logic/behavior along as appropriate. ** Affects: horizon Importance: Undecided Assignee: Matt Borland (palecrow) Status: New ** Changed in: horizon Assignee: (unassigned) => Matt Borland (palecrow) -- 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/1433113 Title: [Launch Instance Fix] Launch wizard from Image pages Status in OpenStack Dashboard (Horizon): New Bug description: The new Launch-Instance wizard is not launched from the Image table or detail screens. The old mechanism needs to be replaced with the new, carrying the original logic/behavior along as appropriate. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1433113/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1433105] [NEW] [Launch Instance Fix] Network Step HTML needs cleanup
Public bug reported: There is a dangling closing dd tag where it should not be. Remove dangling tag and perform any other cleanup needed. ** Affects: horizon Importance: Undecided Assignee: Matt Borland (palecrow) Status: In Progress ** Changed in: horizon Assignee: (unassigned) => Matt Borland (palecrow) -- 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/1433105 Title: [Launch Instance Fix] Network Step HTML needs cleanup Status in OpenStack Dashboard (Horizon): In Progress Bug description: There is a dangling closing dd tag where it should not be. Remove dangling tag and perform any other cleanup needed. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1433105/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
