[Yahoo-eng-team] [Bug 1363704] [NEW] notification registration log should be debug
Public bug reported: When the Keystone server starts, there's several log messages: 2014-08-31 12:45:24.686 INFO keystone.notifications [-] Callback: `keystone.token.provider.Manager._trust_deleted_event_callback` subscribed to event `identity.OS-TRUST:trust.deleted`. ... I can't think of a reason why an administrator would find it necessary to know that some internal callback registrations occurred. If somebody is, they can use logging configuration to enable it. ** Affects: keystone Importance: Low Assignee: Brant Knudson (blk-u) Status: New ** Changed in: keystone Assignee: (unassigned) => Brant Knudson (blk-u) ** Changed in: keystone Milestone: None => juno-3 ** Changed in: keystone Importance: Undecided => Low -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1363704 Title: notification registration log should be debug Status in OpenStack Identity (Keystone): New Bug description: When the Keystone server starts, there's several log messages: 2014-08-31 12:45:24.686 INFO keystone.notifications [-] Callback: `keystone.token.provider.Manager._trust_deleted_event_callback` subscribed to event `identity.OS-TRUST:trust.deleted`. ... I can't think of a reason why an administrator would find it necessary to know that some internal callback registrations occurred. If somebody is, they can use logging configuration to enable it. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1363704/+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 1312971] Re: mod_wsgi exception processing UTF-8 Header
** Also affects: keystone/icehouse Importance: Undecided Status: New ** Changed in: keystone/icehouse Status: New => In Progress ** Changed in: keystone/icehouse Importance: Undecided => High ** Changed in: keystone/icehouse Assignee: (unassigned) => Nathan Kinder (nkinder) ** Changed in: python-keystoneclient Importance: High => Medium -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1312971 Title: mod_wsgi exception processing UTF-8 Header Status in OpenStack Identity (Keystone): Fix Released Status in Keystone icehouse series: In Progress Status in Python client library for Keystone: Triaged Bug description: Using master version of python-keystoneclient (not yet released) gives the following error when running with Keystone in Apache HTTPD and requesting a V3 Token [Fri Apr 25 18:28:14.775659 2014] [:error] [pid 5075] [remote 10.10.63.250:2982] mod_wsgi (pid=5075): Exception occurred processing WSGI script '/var/www/cgi-bin/keystone/main'. [Fri Apr 25 18:28:14.775801 2014] [:error] [pid 5075] [remote 10.10.63.250:2982] TypeError: expected byte string object for header value, value of type unicode found Its due to the utf-8 encoding in keystoneclient/common/cms.py which is making the PKI token Unicode instead of str. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1312971/+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 1363709] [NEW] keystone-all logging config twice
Public bug reported: keystone-all is logging the config twice. Once from keystone-all and once from keystone.openstack.common.service. The config should only has to be logged once. ** Affects: keystone Importance: Low Assignee: Brant Knudson (blk-u) Status: In Progress ** Changed in: keystone Assignee: (unassigned) => Brant Knudson (blk-u) ** Changed in: keystone Milestone: None => juno-3 ** Changed in: keystone Importance: Undecided => Low -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1363709 Title: keystone-all logging config twice Status in OpenStack Identity (Keystone): In Progress Bug description: keystone-all is logging the config twice. Once from keystone-all and once from keystone.openstack.common.service. The config should only has to be logged once. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1363709/+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 1363750] [NEW] Fix the minor comments made during revue of endpoint policy
Public bug reported: There were some minor comments made in the version of the endpoint policy extension that was merged: https://review.openstack.org/#/c/115362/15 This should be tidied up. ** Affects: keystone Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1363750 Title: Fix the minor comments made during revue of endpoint policy Status in OpenStack Identity (Keystone): New Bug description: There were some minor comments made in the version of the endpoint policy extension that was merged: https://review.openstack.org/#/c/115362/15 This should be tidied up. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1363750/+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 1362073] Re: Wrong string format result in exception can't be record into log in nova.virt.disk.vfs.guestfs.
Duplicate with bug https://bugs.launchpad.net/nova/+bug/1352768
Abandon.
** Changed in: nova
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1362073
Title:
Wrong string format result in exception can't be record into log in
nova.virt.disk.vfs.guestfs.
Status in OpenStack Compute (Nova):
Invalid
Bug description:
In current master, nova.virt.disk.vfs.guestfs
136 except AttributeError as ex:
137 # set_backend_settings method doesn't exist in older
138 # libguestfs versions, so nothing we can do but ignore
139 -> LOG.info(_LI("Unable to force TCG mode, libguestfs too
old?"),
140 ex)
141 pass
142
143 try:
144 self.handle.add_drive_opts(self.imgfile,
format=self.imgfmt)
145 self.handle.launch()
Traceback (most recent call last):
File "/usr/lib/python2.7/logging/__init__.py", line 846, in emit
msg = self.format(record)
File "/opt/stack/nova/nova/openstack/common/log.py", line 685, in format
return logging.StreamHandler.format(self, record)
File "/usr/lib/python2.7/logging/__init__.py", line 723, in format
return fmt.format(record)
File "/opt/stack/nova/nova/openstack/common/log.py", line 649, in format
return logging.Formatter.format(self, record)
File "/usr/lib/python2.7/logging/__init__.py", line 464, in format
record.message = record.getMessage()
File "/usr/lib/python2.7/logging/__init__.py", line 328, in getMessage
msg = msg % self.args
TypeError: not all arguments converted during string formatting
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1362073/+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 1363773] [NEW] neutron-ns-metadata-proxy cannot be killed when running in virtual environment
Public bug reported: When running in virtual env, neutron-ns-metadata-proxy on DHCP node cannot be disabled properly when deleting a network. Consequences: 1. Corresponding folder and files under /var/lib/neutron/dhcp/ are not cleaned up. 2. If neutron-dhcp-agent service is restarted in this unclean state, dnsmasq processes are restarted periodically (resync interval), because the failure of removing the deleted networks. (And because of bug 1345947, huge amount of NAK logs flood for dnsmasq.) Root cause: Killing neutron-ns-metadata-proxy is failed because of rootwrapper filter not matched in dhcp_filter.conf: Command: ['sudo', 'neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'kill', '-9', '65832'] Exit code: 99 Stdout: '' Stderr: '/usr/bin/neutron-rootwrap: Unauthorized command: kill -9 65832 (no filter matched)\n' neutron-ns-metadata-proxy is started via ProcessManager, and in Virtual Environment, the python binary under virtual env is used instead of /usr/bin/python*. However, in dhcp_file.conf absolute path is specified for KillerFiler for neutron-ns-metadata-proxy: kill_metadata: KillFilter, root, /usr/bin/python, -9 kill_metadata7: KillFilter, root, /usr/bin/python2.7, -9 kill_metadata6: KillFilter, root, /usr/bin/python2.6, -9 Proposed solution: Do not specify absolute path in filter: use python (or python2.7, or python2.6) instead diff --git a/etc/neutron/rootwrap.d/dhcp.filters b/etc/neutron/rootwrap.d/dhcp.filters index 88d61e8..26c2ffa 100644 --- a/etc/neutron/rootwrap.d/dhcp.filters +++ b/etc/neutron/rootwrap.d/dhcp.filters @@ -29,9 +29,9 @@ metadata_proxy_quantum: CommandFilter, quantum-ns-metadata-proxy, root metadata_proxy_local: CommandFilter, /usr/local/bin/neutron-ns-metadata-proxy, root metadata_proxy_local_quantum: CommandFilter, /usr/local/bin/quantum-ns-metadata-proxy, root # RHEL invocation of the metadata proxy will report /usr/bin/python -kill_metadata: KillFilter, root, /usr/bin/python, -9 -kill_metadata7: KillFilter, root, /usr/bin/python2.7, -9 -kill_metadata6: KillFilter, root, /usr/bin/python2.6, -9 +kill_metadata: KillFilter, root, python, -9 +kill_metadata7: KillFilter, root, python2.7, -9 +kill_metadata6: KillFilter, root, python2.6, -9 # ip_lib ip: IpFilter, ip, root ** Affects: neutron Importance: Undecided Assignee: Han Zhou (zhouhan) Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1363773 Title: neutron-ns-metadata-proxy cannot be killed when running in virtual environment Status in OpenStack Neutron (virtual network service): New Bug description: When running in virtual env, neutron-ns-metadata-proxy on DHCP node cannot be disabled properly when deleting a network. Consequences: 1. Corresponding folder and files under /var/lib/neutron/dhcp/ are not cleaned up. 2. If neutron-dhcp-agent service is restarted in this unclean state, dnsmasq processes are restarted periodically (resync interval), because the failure of removing the deleted networks. (And because of bug 1345947, huge amount of NAK logs flood for dnsmasq.) Root cause: Killing neutron-ns-metadata-proxy is failed because of rootwrapper filter not matched in dhcp_filter.conf: Command: ['sudo', 'neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'kill', '-9', '65832'] Exit code: 99 Stdout: '' Stderr: '/usr/bin/neutron-rootwrap: Unauthorized command: kill -9 65832 (no filter matched)\n' neutron-ns-metadata-proxy is started via ProcessManager, and in Virtual Environment, the python binary under virtual env is used instead of /usr/bin/python*. However, in dhcp_file.conf absolute path is specified for KillerFiler for neutron-ns-metadata-proxy: kill_metadata: KillFilter, root, /usr/bin/python, -9 kill_metadata7: KillFilter, root, /usr/bin/python2.7, -9 kill_metadata6: KillFilter, root, /usr/bin/python2.6, -9 Proposed solution: Do not specify absolute path in filter: use python (or python2.7, or python2.6) instead diff --git a/etc/neutron/rootwrap.d/dhcp.filters b/etc/neutron/rootwrap.d/dhcp.filters index 88d61e8..26c2ffa 100644 --- a/etc/neutron/rootwrap.d/dhcp.filters +++ b/etc/neutron/rootwrap.d/dhcp.filters @@ -29,9 +29,9 @@ metadata_proxy_quantum: CommandFilter, quantum-ns-metadata-proxy, root metadata_proxy_local: CommandFilter, /usr/local/bin/neutron-ns-metadata-proxy, root metadata_proxy_local_quantum: CommandFilter, /usr/local/bin/quantum-ns-metadata-proxy, root # RHEL invocation of the metadata proxy will report /usr/bin/python -kill_metadata: KillFilter, root, /usr/bin/python, -9 -kill_metadata7: KillFilter, root, /usr/bin/python2.7, -9 -kill_metadata6: KillFilter, root, /usr/bin/python2.6, -9 +kill_m
[Yahoo-eng-team] [Bug 1306874] Re: Fix typo of ANS1 to ASN1
** Changed in: django-openstack-auth Milestone: None => 1.1.6 ** Changed in: django-openstack-auth Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1306874 Title: Fix typo of ANS1 to ASN1 Status in Django OpenStack Auth: Fix Released Status in OpenStack Identity (Keystone): Fix Released Status in Python client library for Keystone: Fix Released Bug description: This is really minor but it bugs me everytime I see it referenced in code I'm looking at. The cms code refers to 'ans1' instead of 'asn1', replace all occurrences thereof. Similar changes need to be made in the django_openstack_auth code and keystone v3 auth test. To manage notifications about this bug go to: https://bugs.launchpad.net/django-openstack-auth/+bug/1306874/+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 1308123] Re: Django is pinned to ==1.4 in tox.ini
** Changed in: django-openstack-auth Milestone: None => 1.1.6 ** Changed in: django-openstack-auth Status: Fix Committed => 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/1308123 Title: Django is pinned to ==1.4 in tox.ini Status in Django OpenStack Auth: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Bug description: In the tox.ini file, the configuration for Django 1.4 pins django to ==1.4. We should instead allow the latest stable release of Django 1.4, similarly to how 1.5 is configured. To manage notifications about this bug go to: https://bugs.launchpad.net/django-openstack-auth/+bug/1308123/+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 1302532] Re: docs build for django-based projects should run with DJANGO_SETTINGS_MODULE envvar
** Changed in: django-openstack-auth Milestone: None => 1.1.6 ** Changed in: django-openstack-auth Status: Fix Committed => 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/1302532 Title: docs build for django-based projects should run with DJANGO_SETTINGS_MODULE envvar Status in Django OpenStack Auth: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Core Infrastructure: In Progress Bug description: When running docs build in the gate and post jobs for django-based projects (e.g., horizon, django_openstack_auth, ...), we need to set DJANGO_SETTINGS_MODULE envvar. We can see the following errors in console logs: horizon-docs, gate-horizon-docs: ImproperlyConfigured: The SECRET_KEY setting must not be empty. https://jenkins.openstack.org/view/All/job/horizon-docs/ https://jenkins.openstack.org/view/All/job/gate-horizon-docs/ django-openstack-auth: error: invalid command 'build_sphinx' ERROR: InvocationError: '/home/jenkins/workspace/gate-django_openstack_auth-docs/.tox/venv/bin/python setup.py build_sphinx' It also comes from lack of DJANGO_SETTINGS_MODULES. https://jenkins.openstack.org/view/All/job/gate-django_openstack_auth-docs/ https://jenkins.openstack.org/view/All/job/django_openstack_auth-docs/ To manage notifications about this bug go to: https://bugs.launchpad.net/django-openstack-auth/+bug/1302532/+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 1225662] Re: Log in page: focus should be given to user name field
** Changed in: django-openstack-auth Milestone: None => 1.1.4 ** Changed in: django-openstack-auth Status: Fix Committed => 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/1225662 Title: Log in page: focus should be given to user name field Status in Django OpenStack Auth: Fix Released Status in OpenStack Dashboard (Horizon): Invalid Bug description: When the log in is diplayed the "user name" field should get the focus automatically. To manage notifications about this bug go to: https://bugs.launchpad.net/django-openstack-auth/+bug/1225662/+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 1363805] [NEW] test_ipv6.TestIsEnabled.test_enabled failure
Public bug reported: https://review.openstack.org/#/c/116826/ introduced UT failures on systems without the procfs entry. ** Affects: neutron Importance: Undecided Assignee: YAMAMOTO Takashi (yamamoto) Status: In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1363805 Title: test_ipv6.TestIsEnabled.test_enabled failure Status in OpenStack Neutron (virtual network service): In Progress Bug description: https://review.openstack.org/#/c/116826/ introduced UT failures on systems without the procfs entry. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1363805/+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 1303865] Re: mandatory fields are not enforced in launch stack
The empty name issue looks like a heat bug. The KeyPair resource needs
better validation that the name is between 1 and 255 characters.
The save_private_key error seems reasonable though, an empty string is
not a boolean.
** Also affects: heat
Importance: Undecided
Status: New
** Changed in: heat
Status: New => Triaged
** Changed in: heat
Importance: Undecided => Medium
** Changed in: heat
Milestone: None => juno-3
--
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/1303865
Title:
mandatory fields are not enforced in launch stack
Status in Orchestration API (Heat):
Triaged
Status in OpenStack Dashboard (Horizon):
Triaged
Bug description:
- go to the Create Stack screen, enter the following valid Heat template:
heat_template_version: 2013-05-23
description: >
A single stack with a keypair.
parameters:
key_name:
type: string
default: heat_key3
key_save:
type: string
default: false
resources:
KeyPair:
type: OS::Nova::KeyPair
properties:
name: { get_param: key_name }
save_private_key: { get_param: key_save }
outputs:
PublicKey:
value: { get_attr: [KeyPair, public_key] }
PrivateKey:
value: { get_attr: [KeyPair, private_key] }
- delete one of the fields value (key_name or/and key_save)
=> you will get a message saying "Error: Stack creation failed."
In horizon.log you will get:
2014-04-07 14:49:23,055 7116 DEBUG heatclient.common.http
HTTP/1.1 400 Bad Request
date: Mon, 07 Apr 2014 14:49:23 GMT
content-length: 301
content-type: application/json; charset=UTF-8
{"explanation": "The server could not comply with the request since it
is either malformed or otherwise incorrect.", "code": 400, "error":
{"message": "Property error : KeyPair: save_private_key \"\" is not a
valid boolean", "traceback": null, "type": "StackValidationFailed"},
"title": "Bad Request"}
if any/all of the 2 fields is mandatory, this should be enforced, both
with a message, and with an asterisk, right next to the field.
To manage notifications about this bug go to:
https://bugs.launchpad.net/heat/+bug/1303865/+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 1363809] [NEW] Fix the LinkAction class name for Domain/Projects panel
Public bug reported: The following LinkAction does not describe what it does: -ViewMembersLink -ViewGroupsLink The class name should be update to use "Update" instead of "View". This occurs in both the Project and Domain panels ** Affects: horizon Importance: Undecided Assignee: Lin Hua Cheng (lin-hua-cheng) Status: New ** Changed in: horizon Assignee: (unassigned) => Lin Hua Cheng (lin-hua-cheng) -- 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/1363809 Title: Fix the LinkAction class name for Domain/Projects panel Status in OpenStack Dashboard (Horizon): New Bug description: The following LinkAction does not describe what it does: -ViewMembersLink -ViewGroupsLink The class name should be update to use "Update" instead of "View". This occurs in both the Project and Domain panels To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1363809/+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 1363813] [NEW] Error while running tox
Public bug reported:
When i am running tox on lasted horion code, the tests are failing.
py27dj15 runtests: commands[1] | /bin/bash run_tests.sh -N --no-pep8
Running Horizon application tests
Traceback (most recent call last):
File "/root/horizon/manage.py", line 23, in
execute_from_command_line(sys.argv)
File
"/root/horizon/.tox/py27dj15/local/lib/python2.7/site-packages/django/core/management/__init__.py",
line 453, in execute_from_command_line
utility.execute()
File
"/root/horizon/.tox/py27dj15/local/lib/python2.7/site-packages/django/core/management/__init__.py",
line 392, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File
"/root/horizon/.tox/py27dj15/local/lib/python2.7/site-packages/django/core/management/__init__.py",
line 263, in fetch_command
app_name = get_commands()[subcommand]
File
"/root/horizon/.tox/py27dj15/local/lib/python2.7/site-packages/django/core/management/__init__.py",
line 109, in get_commands
apps = settings.INSTALLED_APPS
File
"/root/horizon/.tox/py27dj15/local/lib/python2.7/site-packages/django/conf/__init__.py",
line 53, in __getattr__
self._setup(name)
File
"/root/horizon/.tox/py27dj15/local/lib/python2.7/site-packages/django/conf/__init__.py",
line 48, in _setup
self._wrapped = Settings(settings_module)
File
"/root/horizon/.tox/py27dj15/local/lib/python2.7/site-packages/django/conf/__init__.py",
line 134, in __init__
raise ImportError("Could not import settings '%s' (Is it on sys.path?): %s"
% (self.SETTINGS_MODULE, e))
ImportError: Could not import settings 'horizon.test.settings' (Is it on
sys.path?): No module named angular
Running openstack_dashboard tests
Traceback (most recent call last):
File "/root/horizon/manage.py", line 23, in
execute_from_command_line(sys.argv)
File
"/root/horizon/.tox/py27dj15/local/lib/python2.7/site-packages/django/core/management/__init__.py",
line 453, in execute_from_command_line
utility.execute()
File
"/root/horizon/.tox/py27dj15/local/lib/python2.7/site-packages/django/core/management/__init__.py",
line 392, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File
"/root/horizon/.tox/py27dj15/local/lib/python2.7/site-packages/django/core/management/__init__.py",
line 263, in fetch_command
app_name = get_commands()[subcommand]
File
"/root/horizon/.tox/py27dj15/local/lib/python2.7/site-packages/django/core/management/__init__.py",
line 109, in get_commands
apps = settings.INSTALLED_APPS
File
"/root/horizon/.tox/py27dj15/local/lib/python2.7/site-packages/django/conf/__init__.py",
line 53, in __getattr__
self._setup(name)
File
"/root/horizon/.tox/py27dj15/local/lib/python2.7/site-packages/django/conf/__init__.py",
line 48, in _setup
self._wrapped = Settings(settings_module)
File
"/root/horizon/.tox/py27dj15/local/lib/python2.7/site-packages/django/conf/__init__.py",
line 134, in __init__
raise ImportError("Could not import settings '%s' (Is it on sys.path?): %s"
% (self.SETTINGS_MODULE, e))
ImportError: Could not import settings 'openstack_dashboard.test.settings' (Is
it on sys.path?): No module named angular
Tests failed.
___ summary
___
ERROR: py26: InterpreterNotFound: python2.6
ERROR: py27: commands failed
ERROR: py27dj14: commands failed
ERROR: py27dj15: commands failed
pep8: commands succeeded
ERROR: py33: InterpreterNotFound: python3.3
** 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/1363813
Title:
Error while running tox
Status in OpenStack Dashboard (Horizon):
New
Bug description:
When i am running tox on lasted horion code, the tests are failing.
py27dj15 runtests: commands[1] | /bin/bash run_tests.sh -N --no-pep8
Running Horizon application tests
Traceback (most recent call last):
File "/root/horizon/manage.py", line 23, in
execute_from_command_line(sys.argv)
File
"/root/horizon/.tox/py27dj15/local/lib/python2.7/site-packages/django/core/management/__init__.py",
line 453, in execute_from_command_line
utility.execute()
File
"/root/horizon/.tox/py27dj15/local/lib/python2.7/site-packages/django/core/management/__init__.py",
line 392, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File
"/root/horizon/.tox/py27dj15/local/lib/python2.7/site-packages/django/core/management/__init__.py",
line 263, in fetch_command
app_name = get_commands()[subcommand]
File
"/root/horizon/.tox/py27dj15/local/lib/python2.7/site-packages/django/core/management/__init__.py",
line 109, in get_commands
apps = settings.INSTALLED_APPS
File
"/root/horizon/.tox/py27dj15/
