[Yahoo-eng-team] [Bug 1596829] Re: String interpolation should be delayed at logging calls
** No longer affects: sahara
--
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/1596829
Title:
String interpolation should be delayed at logging calls
Status in congress:
Fix Released
Status in Glance:
In Progress
Status in glance_store:
In Progress
Status in OpenStack Dashboard (Horizon):
Fix Released
Status in Ironic:
Fix Released
Status in masakari:
Fix Released
Status in networking-vsphere:
Fix Released
Status in OpenStack Compute (nova):
Fix Released
Status in os-brick:
Fix Released
Status in os-vif:
Fix Released
Status in python-cinderclient:
Fix Released
Status in Glance Client:
Fix Released
Status in python-manilaclient:
Fix Released
Status in python-openstackclient:
Fix Released
Status in python-troveclient:
In Progress
Status in senlin:
Invalid
Bug description:
String interpolation should be delayed to be handled by the logging
code, rather than being done at the point of the logging call.
Wrong: LOG.debug('Example: %s' % 'bad')
Right: LOG.debug('Example: %s', 'good')
See the following guideline.
* http://docs.openstack.org/developer/oslo.i18n/guidelines.html
#adding-variables-to-log-messages
The rule for it should be added to hacking checks.
To manage notifications about this bug go to:
https://bugs.launchpad.net/congress/+bug/1596829/+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 1676486] [NEW] Update row in glance images doesn't work
Public bug reported: Update row in glance images doesn't work, and it hangs in the 'Saving' state. Steps to reproduce: 1. Create an image. 2. Doesn't refresh the table. Image will stay in the 'Saving' or 'Queued' state. ** 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/1676486 Title: Update row in glance images doesn't work Status in OpenStack Dashboard (Horizon): New Bug description: Update row in glance images doesn't work, and it hangs in the 'Saving' state. Steps to reproduce: 1. Create an image. 2. Doesn't refresh the table. Image will stay in the 'Saving' or 'Queued' state. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1676486/+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 1427328] Re: [UI] The mechanism used to avoid duplicate script names in jobs binaries is fragile
We no longer fixing stuff around internals. ** Changed in: sahara Status: Confirmed => Won't Fix ** Changed in: sahara Importance: Wishlist => Undecided -- 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/1427328 Title: [UI] The mechanism used to avoid duplicate script names in jobs binaries is fragile Status in OpenStack Dashboard (Horizon): Invalid Status in Sahara: Won't Fix Bug description: Create a Job Binary in the internal db, with a specific script name (for example, "script_name"). If the user creates another job binary with the same script name, a unique UUID is added so that the name is unique. But, if the script name is long, the addition of the UUID can make it longer than the field limit (80 characters) and the job creation fails. Moreover, this mechanism is counterintuitive as it is not implemented for the job binary "name" field (an error is returned). Proposal: - remove the mechanism which tries to create an unique script name, and simply returns a validation error if a script name is duplicated. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1427328/+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 1427304] Re: [UI] When the job binary creating fails, the job binary data is created anyway
We no longer fixing stuff around internals. ** Changed in: sahara Status: Incomplete => 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/1427304 Title: [UI] When the job binary creating fails, the job binary data is created anyway Status in OpenStack Dashboard (Horizon): Invalid Status in Sahara: Won't Fix Bug description: If the user tries to create a Job Binary using the internal db as storage, and the creating fails for a validation error, the job binary data is created anyway. The job data creation code should be executed at the same time/in the same transaction of the job binary creation (and rolled back if the latter fails). Found on current Horizon git master (Sahara from Juno, but the problem seems more Horizon-related). To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1427304/+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 1082248] Re: Use uuidutils instead of uuid.uuid4()
I think that we really don't need a bug for this. Just a minor improvement. ** Changed in: sahara Status: New => Invalid ** No longer affects: sahara -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1082248 Title: Use uuidutils instead of uuid.uuid4() Status in neutron: Fix Released Status in OpenStack Compute (nova): New Bug description: Openstack common has a wrapper for generating uuids. We should only use that function when generating uuids for consistency. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1082248/+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 1628597] Re: Support upper-constraints in tox.ini
Please no, don't assign all projects to issue. it is absolutely useless.
Moreover, I think that there is no sense in bug at all. So, making as no
longer affects sahara.
** No longer affects: sahara
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1628597
Title:
Support upper-constraints in tox.ini
Status in OpenStack Designate Charm:
New
Status in cloudbase-init:
New
Status in congress:
New
Status in craton:
New
Status in diskimage-builder:
New
Status in freezer-web-ui:
New
Status in Karbor:
In Progress
Status in kolla:
New
Status in masakari:
New
Status in neutron:
New
Status in python-cinderclient:
New
Status in python-heatclient:
New
Status in python-smaugclient:
New
Status in python-keystoneclient:
New
Status in python-mistralclient:
New
Status in python-searchlightclient:
New
Status in python-solumclient:
New
Status in python-swiftclient:
New
Status in python-tackerclient:
New
Status in Vitrage Client:
New
Status in Rally:
New
Status in OpenStack Search (Searchlight):
Fix Released
Status in Solum:
New
Status in storlets:
New
Status in tempest:
New
Status in tripleo-common:
New
Status in trove-dashboard:
New
Status in Vitrage:
New
Bug description:
tox.ini needs to respect upper-constraints in order to pin CI jobs as
time goes on.
This is as simple as adding to install_command:
-c{env:UPPER_CONSTRAINTS_FILE:https://git.openstack.org/cgit/openstack/requirements/plain
/upper-constraints.txt}
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-designate/+bug/1628597/+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 1563419] Re: [UI] sahara uses UTC time instead of set timezone
** Changed in: sahara/mitaka 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/1563419 Title: [UI] sahara uses UTC time instead of set timezone Status in OpenStack Dashboard (Horizon): Invalid Status in Sahara: Fix Released Status in Sahara mitaka series: Fix Released Bug description: All time values that are shown in sahara dashboard are in UTC no matter what kind of timezone we have set in settings. It affects the Data Sources, Job Execution detail views and Cluster provision steps table To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1563419/+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 1613542] Re: tempest.conf doesn't contain $project in [service_available] section
** No longer affects: sahara
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1613542
Title:
tempest.conf doesn't contain $project in [service_available] section
Status in Aodh:
Fix Released
Status in Ceilometer:
In Progress
Status in ec2-api:
In Progress
Status in Gnocchi:
In Progress
Status in Ironic:
In Progress
Status in Ironic Inspector:
In Progress
Status in OpenStack Identity (keystone):
In Progress
Status in Magnum:
Fix Released
Status in neutron:
New
Status in OpenStack Data Processing ("Sahara") sahara-tests:
New
Status in vmware-nsx:
In Progress
Bug description:
When generating the tempest conf, the tempest plugins need to register the
config options.
But for the [service_available] section, ceilometer (and the other mentioned
projects) doesn't register any value so it's missng in the tempest sample
config.
Steps to reproduce:
$ tox -egenconfig
$ source .tox/genconfig/bin/activate
$ oslo-config-generator --config-file
.tox/genconfig/lib/python2.7/site-packages/tempest/cmd/config-generator.tempest.conf
--output-file tempest.conf.sample
Now check the [service_available] section from tempest.conf.sample
To manage notifications about this bug go to:
https://bugs.launchpad.net/aodh/+bug/1613542/+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 1394794] Re: [UI] Internal error during cluster deletion
** Changed in: sahara Status: Incomplete => 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/1394794 Title: [UI] Internal error during cluster deletion Status in OpenStack Dashboard (Horizon): Invalid Status in Sahara: Invalid Bug description: I had 3 clusters I wanted to delete. I marked all three of them and clicked 'delete clusters'. After some time 'Failed to update row' message occurred on client side. Stacktrace from horizon: Internal Server Error: /project/data_processing/clusters/ Traceback (most recent call last): File "/Users/alazarev/openstack/horizon/.venv/lib/python2.7/site-packages/django/core/handlers/base.py", line 112, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/Users/alazarev/openstack/horizon/horizon/decorators.py", line 36, in dec return view_func(request, *args, **kwargs) File "/Users/alazarev/openstack/horizon/horizon/decorators.py", line 52, in dec return view_func(request, *args, **kwargs) File "/Users/alazarev/openstack/horizon/horizon/decorators.py", line 36, in dec return view_func(request, *args, **kwargs) File "/Users/alazarev/openstack/horizon/horizon/decorators.py", line 84, in dec return view_func(request, *args, **kwargs) File "/Users/alazarev/openstack/horizon/.venv/lib/python2.7/site-packages/django/views/generic/base.py", line 69, in view return self.dispatch(request, *args, **kwargs) File "/Users/alazarev/openstack/horizon/.venv/lib/python2.7/site-packages/django/views/generic/base.py", line 87, in dispatch return handler(request, *args, **kwargs) File "/Users/alazarev/openstack/horizon/horizon/tables/views.py", line 157, in get handled = self.construct_tables() File "/Users/alazarev/openstack/horizon/horizon/tables/views.py", line 143, in construct_tables preempted = table.maybe_preempt() File "/Users/alazarev/openstack/horizon/horizon/tables/base.py", line 1518, in maybe_preempt error = exceptions.handle(request, ignore=True) File "/Users/alazarev/openstack/horizon/horizon/exceptions.py", line 334, in handle six.reraise(exc_type, exc_value, exc_traceback) File "/Users/alazarev/openstack/horizon/horizon/tables/base.py", line 1511, in maybe_preempt if self.get_object_id(datum) == self.current_item_id: File "/Users/alazarev/openstack/horizon/horizon/tables/base.py", line 1655, in get_object_id return datum.id AttributeError: 'NoneType' object has no attribute 'id' [20/Nov/2014 23:20:12] "GET /project/data_processing/clusters/?action=row_update=clusters_id=9a43709b-d998-4a14-be38-8318a44821d7 HTTP/1.1" 200 1019 [20/Nov/2014 23:20:13] "GET /project/data_processing/clusters/?action=row_update=clusters_id=8608c1ba-bb45-4a85-9734-fd602770cba4 HTTP/1.1" 500 31829 No errors on sahara side. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1394794/+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 1391698] Re: [UI] Sahara should handle 100 response on row update
** Changed in: sahara Status: Incomplete => 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/1391698 Title: [UI] Sahara should handle 100 response on row update Status in OpenStack Dashboard (Horizon): Invalid Status in Sahara: Invalid Bug description: I created cluster and was waiting while it is Active. After some time I observed in Sahara logs that cluster is already Active. In Horizon it was still in Starting state and didn't update. Here what I see in horizon logs: [12/Nov/2014 00:07:13] "GET /project/data_processing/clusters/?action=row_update=clusters_id=e11d0970-2163-4521-92e3-25671087f633 HTTP/1.1" 200 1033 [12/Nov/2014 00:07:15] "GET /project/data_processing/clusters/?action=row_update=clusters_id=e11d0970-2163-4521-92e3-25671087f633 HTTP/1.1" 200 1033 [12/Nov/2014 00:07:20] "GET /project/data_processing/clusters/?action=row_update=clusters_id=e11d0970-2163-4521-92e3-25671087f633 HTTP/1.1" 100 0 It looks like horizon stops updating cluster table row after 100 response. I'm not sure why server responded 100, but this is definitely wrong behavior either of server side (must not respond with 100 or should log why this happened) or client side (100 is a valid response and should not be treated as fatal error). Error from javascript log: Failed to load resource: net::ERR_EMPTY_RESPONSE http://localhost:8080/project/data_processing/clusters/?action=row_update=clusters_id=e11d0970-2163-4521-92e3-25671087f633 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1391698/+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 1551009] Re: dashboard: Invalid template Invalid filter: 'parse_isotime'
** 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/1551009
Title:
dashboard: Invalid template Invalid filter: 'parse_isotime'
Status in OpenStack Dashboard (Horizon):
Invalid
Status in Sahara:
Fix Released
Bug description:
When running "python manage.py compress --force" in an environment where
sahara-dasahboard is enabled,
the following error message is shown.
This bug is about 'parse_isotime'.
Note that bug 1551006 is about Could not parse the remainder: '{{' from '{{'
because the cause seems different.
$ DJANGO_SETTINGS_MODULE=openstack_dashboard.settings python manage.py
compress --force
Invalid template
/opt/stack/sahara-dashboard/sahara_dashboard/content/data_processing/jobs/templates/job_templates/_details.html:
Invalid filter: 'parse_isotime'
Invalid template
/opt/stack/sahara-dashboard/sahara_dashboard/content/data_processing/clusters/templates/cluster_templates/create.html:
Could not parse the remainder: '{{' from '{{'
Invalid template
/opt/stack/sahara-dashboard/sahara_dashboard/content/data_processing/clusters/templates/nodegroup_templates/create.html:
Could not parse the remainder: '{{' from '{{'
Invalid template
/opt/stack/sahara-dashboard/sahara_dashboard/content/data_processing/jobs/templates/job_binaries/_details.html:
Invalid filter: 'parse_isotime'
Found 'compress' tags in:
/opt/stack/horizon/openstack_dashboard/templates/horizon/_scripts.html
/opt/stack/horizon/openstack_dashboard/templates/horizon/_conf.html
/opt/stack/horizon/openstack_dashboard/templates/_stylesheets.html
Compressing... done
Compressed 5 block(s) from 3 template(s) for 2 context(s).
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1551009/+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 1563419] Re: [UI] sahara uses UTC time instead of set timezone
** Changed in: horizon Status: In Progress => 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/1563419 Title: [UI] sahara uses UTC time instead of set timezone Status in OpenStack Dashboard (Horizon): Invalid Status in Sahara: Fix Released Status in Sahara mitaka series: Fix Committed Bug description: All time values that are shown in sahara dashboard are in UTC no matter what kind of timezone we have set in settings. It affects the Data Sources, Job Execution detail views and Cluster provision steps table To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1563419/+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 1588795] Re: Error when trying to show details of cluster from other tenants (is_public = True)
** Changed in: horizon
Status: New => Invalid
** Also affects: sahara
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/1588795
Title:
Error when trying to show details of cluster from other tenants
(is_public = True)
Status in OpenStack Dashboard (Horizon):
Invalid
Status in Sahara:
New
Bug description:
Error with sahara-dashboard
To reproduce:
-1 create a cluster
-2 make it public
-3 change your tenant
-4 try to click on the previously created cluster to show details.
Error:
Error during template rendering
In template
/home/horizon/horizon/.venv/local/lib/python2.7/site-packages/sahara_dashboard/content/data_processing/clusters/templates/clusters/_details.html,
error at line 32
Reverse for 'plugin-details' with arguments '('',)' and keyword arguments
'{}' not found. 1 pattern(s) tried:
[u'project/data_processing/jobs/plugin/(?P[^/]+)$']
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1588795/+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 1568708] Re: translation sync broken due to wrong usage of venv
** Changed in: sahara/mitaka Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1568708 Title: translation sync broken due to wrong usage of venv Status in networking-midonet: In Progress Status in networking-ovn: Confirmed Status in neutron: Fix Committed Status in Sahara: Fix Released Status in Sahara mitaka series: Fix Released Bug description: post jobs cannot use zuul-cloner and have no access currently to upper-constraints. See how nova or neutron itself handle this. Right now the sync with translations fails: https://jenkins.openstack.org/job/neutron-fwaas-propose-translation- update/119/console Please fix venv tox environment. To manage notifications about this bug go to: https://bugs.launchpad.net/networking-midonet/+bug/1568708/+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 1568708] Re: translation sync broken due to wrong usage of venv
** Also affects: sahara/mitaka Importance: Undecided Status: New ** Changed in: sahara/mitaka Importance: Undecided => High ** Changed in: sahara/mitaka Assignee: (unassigned) => Vitaly Gridnev (vgridnev) ** Changed in: sahara/mitaka Status: New => 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/1568708 Title: translation sync broken due to wrong usage of venv Status in networking-midonet: In Progress Status in networking-ovn: Confirmed Status in neutron: Fix Committed Status in Sahara: Fix Released Status in Sahara mitaka series: In Progress Bug description: post jobs cannot use zuul-cloner and have no access currently to upper-constraints. See how nova or neutron itself handle this. Right now the sync with translations fails: https://jenkins.openstack.org/job/neutron-fwaas-propose-translation- update/119/console Please fix venv tox environment. To manage notifications about this bug go to: https://bugs.launchpad.net/networking-midonet/+bug/1568708/+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 1563419] Re: [UI] sahara uses UTC time instead of set timezone
http://docs.openstack.org/project-team-guide/stable-branches.html ** Also affects: sahara/mitaka 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/1563419 Title: [UI] sahara uses UTC time instead of set timezone Status in OpenStack Dashboard (Horizon): New Status in Sahara: Fix Released Status in Sahara mitaka series: New Bug description: All time values that are shown in sahara dashboard are in UTC no matter what kind of timezone we have set in settings. It affects the Data Sources, Job Execution detail views and Cluster provision steps table To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1563419/+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 1503501] Re: oslo.db no longer requires testresources and testscenarios packages
** Changed in: sahara/liberty
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1503501
Title:
oslo.db no longer requires testresources and testscenarios packages
Status in Cinder:
Fix Released
Status in Glance:
Fix Released
Status in heat:
Fix Released
Status in heat liberty series:
Fix Released
Status in Ironic:
Fix Released
Status in neutron:
Fix Released
Status in OpenStack Compute (nova):
Fix Released
Status in Sahara:
Fix Released
Status in Sahara liberty series:
Fix Released
Status in Sahara mitaka series:
Fix Released
Bug description:
As of https://review.openstack.org/#/c/217347/ oslo.db no longer has
testresources or testscenarios in its requirements, So next release of
oslo.db will break several projects. These project that use fixtures
from oslo.db should add these to their requirements if they need it.
Example from Nova:
${PYTHON:-python} -m subunit.run discover -t ./ ${OS_TEST_PATH:-./nova/tests}
--list
---Non-zero exit code (2) from test listing.
error: testr failed (3)
import errors ---
Failed to import test module: nova.tests.unit.db.test_db_api
Traceback (most recent call last):
File
"/home/travis/build/dims/nova/.tox/py27/lib/python2.7/site-packages/unittest2/loader.py",
line 456, in _find_test_path
module = self._get_module_from_name(name)
File
"/home/travis/build/dims/nova/.tox/py27/lib/python2.7/site-packages/unittest2/loader.py",
line 395, in _get_module_from_name
__import__(name)
File "nova/tests/unit/db/test_db_api.py", line 31, in
from oslo_db.sqlalchemy import test_base
File
"/home/travis/build/dims/nova/.tox/py27/src/oslo.db/oslo_db/sqlalchemy/test_base.py",
line 17, in
import testresources
ImportError: No module named testresources
https://travis-ci.org/dims/nova/jobs/83992423
To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1503501/+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 1456250] Re: [UI] launch job configuration preset names are incorrect
** Changed in: sahara Status: Incomplete => 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/1456250 Title: [UI] launch job configuration preset names are incorrect Status in OpenStack Dashboard (Horizon): Invalid Status in Sahara: Invalid Bug description: When we launch a job by a job_template, e.g., a hive job_template, go to "Configure" tab, and click "Add" under Configuration, then click the "Name" input box, you are supposed to get a default key list. However, you get a default value list. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1456250/+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 1501116] Re: "Image Registry" window contains a text box which overlaps with buttons (Japanese and German)
@Sharat, why it's moved to fix released? ** Changed in: sahara Status: Fix Released => 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/1501116 Title: "Image Registry" window contains a text box which overlaps with buttons (Japanese and German) Status in OpenStack Dashboard (Horizon): Invalid Status in Sahara: New Bug description: Project > Data Processing > Image Registry > Register Image The "Register Image" window, "Image Registry tool" text box becomes larger when it contains translated text (only confirmed in German and Japanese, but could be affecting more languages). It overlaps with buttons and other text. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1501116/+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 1430232] Re: [UI] In "Job execution" i can select cluster in "Error" state
Moving to invalid in favour of the blueprint https://blueprints.launchpad.net/sahara/+spec/cluster-choice-for-jobs ** Changed in: sahara Status: In Progress => Invalid ** Changed in: sahara Importance: Low => Undecided ** Changed in: sahara Assignee: Michael Ionkin (msionkin) => (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/1430232 Title: [UI] In "Job execution" i can select cluster in "Error" state Status in OpenStack Dashboard (Horizon): Invalid Status in Sahara: Invalid Bug description: ENVIRONMENT: devstack STEPS TO REPRODUCE: 1. Create Vanilla2 cluster 2. Create wrong cluster and retain in "Error" state 3. Create Job 4. Click on "Launch on existing cluster" ACTUAL RESULT: In "Cluster" i can select all clusters EXPECTED RESULT: In "Cluster" i can select clusters in only "Active" state To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1430232/+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 1276694] Re: Openstack services should support SIGHUP signal
Sahara uses oslo.service for launching sahara. Moving to Fix Released
because of that
** Changed in: sahara
Status: In Progress => Fix Released
** Changed in: sahara
Milestone: next => mitaka-3
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1276694
Title:
Openstack services should support SIGHUP signal
Status in Cinder:
Invalid
Status in Glance:
Fix Released
Status in heat:
Fix Released
Status in OpenStack Identity (keystone):
Invalid
Status in Murano:
Confirmed
Status in neutron:
In Progress
Status in OpenStack Compute (nova):
Fix Released
Status in oslo-incubator:
Invalid
Status in oslo.config:
Fix Released
Status in oslo.log:
Fix Released
Status in oslo.service:
Fix Released
Status in Sahara:
Fix Released
Bug description:
1)In order to more effectively manage the unlinked and open (lsof +L1)
log files descriptors w/o restarting the services, SIGHUP signal
should be accepted by every Openstack service.
That would allow, e.g. logrotate jobs to gracefully HUP services after
their log files were rotated. The only option we have for now is to
force the services restart, quite a poor option from the services
continuous accessibility PoV.
Note: according to http://en.wikipedia.org/wiki/Unix_signal
SIGHUP
... Many daemons will reload their configuration files and reopen their
logfiles instead of exiting when receiving this signal.
Currently Murano and Glance are out of sync with Oslo SIGHUP support.
There is also the following issue exists for some of the services of OS
projects with synced SIGHUP support:
2)
heat-api-cfn, heat-api, heat-api-cloudwatch, keystone: looks like the synced
code is never being executed, thus SIGHUP is not supported for them. Here is a
simple test scenario:
2.1) modify
/site-packages//openstack/common/service.py
def _sighup_supported():
+LOG.warning("SIGHUP is supported: {0}".format(hasattr(signal, 'SIGHUP')))
return hasattr(signal, 'SIGHUP')
2.2) restart service foo-service-name and check logs for "SIGHUP is
supported", if service really supports it, the appropriate messages would be
present in the logs.
2.3) issue kill -HUP and check logs for "SIGHUP is
supported" and "Caught SIGHUP", if service really supports it, the appropriate
messages would be present in the logs. Besides that, the service should remain
started and its main thread PID should not be changed.
e.g.
2.a) heat-engine supports HUPing:
#service openstack-heat-engine restart
<132>Apr 11 14:03:48 node-3 heat-heat.openstack.common.service WARNING:
SIGHUP is supported: True
2.b)But heat-api don't know how to HUP:
#service openstack-heat-api restart
<134>Apr 11 14:06:22 node-3 heat-heat.api INFO: Starting Heat ReST API on
0.0.0.0:8004
<134>Apr 11 14:06:22 node-3 heat-eventlet.wsgi.server INFO: Starting single
process server
2.c) HUPing heat-engine is OK
#pid=$(cat /var/run/heat/openstack-heat-engine.pid); kill -HUP $pid && echo
$pid
16512
<134>Apr 11 14:12:15 node-3 heat-heat.openstack.common.service INFO: Caught
SIGHUP, exiting
<132>Apr 11 14:12:15 node-3 heat-heat.openstack.common.service WARNING:
SIGHUP is supported: True
<134>Apr 11 14:12:15 node-3 heat-heat.openstack.common.rpc.common INFO:
Connected to AMQP server on ...
service openstack-heat-engine status
openstack-heat-engine (pid 16512) is running...
2.d) HUPed heat-api is dead now ;(
#kill -HUP $(cat /var/run/heat/openstack-heat-api.pid)
(no new logs)
# service openstack-heat-api status
openstack-heat-api dead but pid file exists
3)
nova-cert, nova-novncproxy, nova-objectstore, nova-consoleauth,
nova-scheduler - unlike to case 2, after kill -HUP command
was issued, there would be a "Caught SIGHUP" message in the logs, BUT the
associated service would have got dead anyway. Instead, the service should
remain started and its main thread PID should not be changed (similar to the
2.c case).
So, looks like there are a lot of things still should be done to
ensure POSIX standards abidance in Openstack :-)
To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1276694/+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 1505271] Re: Information about volumes not displayed in cluster template and cluster information
** Project changed: horizon => sahara ** Summary changed: - Information about volumes not displayed in cluster template and cluster information + [UI] Information about volumes not displayed in cluster template and cluster information ** Tags removed: sahara ** Tags added: dashboard -- 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/1505271 Title: [UI] Information about volumes not displayed in cluster template and cluster information Status in Sahara: Confirmed Bug description: ENVIRONMENT: devstack(12.10.2015) STEPS TO REPRODUCE: 1. Create node groups with volumes 2. Create cluster template with these node groups 3. Create cluster with this cluster template 4. Click on cluster 5. Click on "Node Groups" EXPECTED RESULT: In information about node group exist information about volumes ACTUAL RESULT: Information about volumes not exist To manage notifications about this bug go to: https://bugs.launchpad.net/sahara/+bug/1505271/+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 1368661] Re: Unit tests sometimes fail because of stale pyc files
** Changed in: python-saharaclient Importance: Undecided => Low ** Changed in: python-saharaclient Status: Fix Committed => Fix Released -- 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/1368661 Title: Unit tests sometimes fail because of stale pyc files Status in congress: Fix Released Status in Gnocchi: Invalid Status in Ironic: Fix Released Status in Magnum: Fix Released Status in Mistral: Fix Released Status in Monasca: Fix Committed Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) icehouse series: Fix Released Status in oslo.cache: Invalid Status in oslo.concurrency: Invalid Status in oslo.service: Fix Committed Status in python-cinderclient: Fix Released Status in python-congressclient: Fix Released Status in python-cueclient: Fix Released Status in python-glanceclient: In Progress Status in python-heatclient: Fix Committed Status in python-keystoneclient: Fix Released Status in python-magnumclient: Fix Released Status in python-mistralclient: Fix Committed Status in python-neutronclient: Fix Released Status in Python client library for Sahara: Fix Released Status in python-solumclient: Fix Released Status in python-swiftclient: Fix Released Status in python-troveclient: Fix Committed Status in Python client library for Zaqar: Fix Committed Status in Solum: Fix Released Status in OpenStack Object Storage (swift): In Progress Status in Trove: Fix Released Status in zaqar: Fix Released Bug description: Because python creates pyc files during tox runs, certain changes in the tree, like deletes of files, or switching branches, can create spurious errors. This can be suppressed by PYTHONDONTWRITEBYTECODE=1 in the tox.ini. To manage notifications about this bug go to: https://bugs.launchpad.net/congress/+bug/1368661/+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 1529534] Re: User new log style where Logger.exception() is used by passing an exception object as the first argument.
** No longer affects: sahara -- 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/1529534 Title: User new log style where Logger.exception() is used by passing an exception object as the first argument. Status in Cinder: Invalid Status in Magnum: Fix Released Status in OpenStack Compute (nova): In Progress Status in python-glanceclient: New Status in python-keystoneclient: New Status in python-neutronclient: In Progress Status in python-troveclient: New Status in Trove: New Bug description: Use new log style where Logger.exception() is used by passing an exception object as the first argument[1]. [1]http://docs.openstack.org/developer/oslo.log/usage.html#no-more- implicit-conversion-to-unicode-str To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1529534/+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 1488913] Re: Deprecation warnings (removal in Django 1.8) in Data Processing
** 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/1488913 Title: Deprecation warnings (removal in Django 1.8) in Data Processing Status in OpenStack Dashboard (Horizon): Invalid Bug description: Noticed below message in logs in Data Processing panels: WARNING:py.warnings:RemovedInDjango18Warning: In Django 1.8, widget attribute placeholder=True will be rendered as 'placeholder'. To preserve current behavior, use the string 'True' instead of the boolean value. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1488913/+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 1509121] Re: [UI] job_binaries Exception Value: too many values to unpack
** Also 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/1509121
Title:
[UI] job_binaries Exception Value: too many values to unpack
Status in OpenStack Dashboard (Horizon):
New
Status in Sahara:
Fix Released
Bug description:
I accidentally created a Sahara EDP Job Binary, in RDO Kilo, with the
following properties:
Name
Binary
ID
c1fa1a5b-2458-43cc-9fbc-52a54fe74009
URL
swift://swift://container.sahara/Test-Private-Container/
Description
None
When I try to "Delete the Job Binary" the Dashboard displays a full-
page exception. Here is the Traceback:
Environment:
Request Method: POST
Request URL: https://my.org/dashboard/project/data_processing/job_binaries/
Django Version: 1.8.3
Python Version: 2.7.5
Installed Applications:
['openstack_dashboard.dashboards.project',
'openstack_dashboard.dashboards.admin',
'openstack_dashboard.dashboards.identity',
'openstack_dashboard.dashboards.settings',
'openstack_dashboard',
'django.contrib.contenttypes',
'django.contrib.auth',
'django.contrib.sessions',
'django.contrib.messages',
'django.contrib.staticfiles',
'django.contrib.humanize',
'django_pyscss',
'openstack_dashboard.django_pyscss_fix',
'compressor',
'horizon',
'openstack_auth']
Installed Middleware:
('django.middleware.common.CommonMiddleware',
'django.middleware.csrf.CsrfViewMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.contrib.messages.middleware.MessageMiddleware',
'django.contrib.auth.middleware.SessionAuthenticationMiddleware',
'horizon.middleware.HorizonMiddleware',
'django.middleware.locale.LocaleMiddleware',
'django.middleware.clickjacking.XFrameOptionsMiddleware')
Traceback:
File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py" in
get_response
132. response = wrapped_callback(request,
*callback_args, **callback_kwargs)
File "/usr/lib/python2.7/site-packages/horizon/decorators.py" in dec
36. return view_func(request, *args, **kwargs)
File "/usr/lib/python2.7/site-packages/horizon/decorators.py" in dec
52. return view_func(request, *args, **kwargs)
File "/usr/lib/python2.7/site-packages/horizon/decorators.py" in dec
36. return view_func(request, *args, **kwargs)
File "/usr/lib/python2.7/site-packages/horizon/decorators.py" in dec
84. return view_func(request, *args, **kwargs)
File "/usr/lib/python2.7/site-packages/django/views/generic/base.py" in view
71. return self.dispatch(request, *args, **kwargs)
File "/usr/lib/python2.7/site-packages/django/views/generic/base.py" in
dispatch
89. return handler(request, *args, **kwargs)
File "/usr/lib/python2.7/site-packages/horizon/tables/views.py" in post
223. return self.get(request, *args, **kwargs)
File "/usr/lib/python2.7/site-packages/horizon/tables/views.py" in get
159. handled = self.construct_tables()
File "/usr/lib/python2.7/site-packages/horizon/tables/views.py" in
construct_tables
150. handled = self.handle_table(table)
File "/usr/lib/python2.7/site-packages/horizon/tables/views.py" in
handle_table
125. handled = self._tables[name].maybe_handle()
File "/usr/lib/python2.7/site-packages/horizon/tables/base.py" in maybe_handle
1640. return self.take_action(action_name, obj_id)
File "/usr/lib/python2.7/site-packages/horizon/tables/base.py" in take_action
1482. response = action.multiple(self, self.request,
obj_ids)
File "/usr/lib/python2.7/site-packages/horizon/tables/actions.py" in multiple
302. return self.handle(data_table, request, object_ids)
File "/usr/lib/python2.7/site-packages/horizon/tables/actions.py" in handle
827. exceptions.handle(request, ignore=ignore)
File "/usr/lib/python2.7/site-packages/horizon/exceptions.py" in handle
364. six.reraise(exc_type, exc_value, exc_traceback)
File "/usr/lib/python2.7/site-packages/horizon/tables/actions.py" in handle
811. self.action(request, datum_id)
File "/usr/lib/python2.7/site-packages/horizon/tables/actions.py" in action
926. return self.delete(request, obj_id)
File
"/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/dashboards/project/data_processing/job_binaries/tables.py"
in delete
56. (jb_type, jb_internal_id) = jb.url.split("://")
Exception Type: ValueError at /project/data_processing/job_binaries/
Exception Value: too many values to unpack
To manage notifications about this bug go to:
[Yahoo-eng-team] [Bug 1470559] Re: Details Tab for a Sahara Cluster shows too much Cluster Configs
** Project changed: horizon => sahara ** Summary changed: - Details Tab for a Sahara Cluster shows too much Cluster Configs + [UI] Details Tab for a Sahara Cluster shows too much Cluster Configs ** Changed in: sahara Importance: Undecided => Medium ** Changed in: sahara Milestone: None => mitaka-2 ** Tags removed: sahara ** Tags added: dashboard -- 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/1470559 Title: [UI] Details Tab for a Sahara Cluster shows too much Cluster Configs Status in Sahara: In Progress Bug description: The Cluster Configs are rendered on the details tab of the Clusters. It means that if there are many Services supported the page will grow with almost useless information. It will be better to move the Cluster configs to a separate Tab. To manage notifications about this bug go to: https://bugs.launchpad.net/sahara/+bug/1470559/+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 1502854] Re: Cannot get information about job on fake plugin with empty datasources
** Project changed: horizon => sahara ** Tags added: dashboard ** Summary changed: - Cannot get information about job on fake plugin with empty datasources + [UI] Cannot get information about job on fake plugin with empty datasources ** Changed in: sahara Importance: Undecided => Low ** Changed in: sahara Milestone: None => mitaka-2 -- 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/1502854 Title: [UI] Cannot get information about job on fake plugin with empty datasources Status in Sahara: In Progress Bug description: ENVIRONMENT: devstack (05.10.2015) STEPS TO REPRODUCE: 1. Create fake cluster 2. Run job without datasources 3. Wait while job passed 4. Click on job EXPECTED RESULT: Get information about job ACTUAL TESULT: http://paste.openstack.org/show/475283/ To manage notifications about this bug go to: https://bugs.launchpad.net/sahara/+bug/1502854/+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 1512207] Re: Fix usage of assertions
** Also affects: sahara Importance: Undecided Status: New ** Changed in: sahara Status: New => In Progress ** Changed in: sahara Importance: Undecided => Low -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1512207 Title: Fix usage of assertions Status in OpenStack Identity (keystone): Fix Committed Status in Manila: In Progress Status in Sahara: In Progress Bug description: Manila should use the specific assertion: self.assertIsTrue/False(observed) instead of the generic assertion: self.assertEqual(True/False, observed) To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1512207/+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 1488218] [NEW] [Sahara] Cannot choose libs for Java job type
Public bug reported: Java job type can require extra libs during execution. Now I cannot choose any libs for that job type ** Affects: horizon Importance: Undecided Assignee: Vitaly Gridnev (vgridnev) Status: In Progress ** Tags: sahara ** Tags added: sahara -- 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/1488218 Title: [Sahara] Cannot choose libs for Java job type Status in OpenStack Dashboard (Horizon): In Progress Bug description: Java job type can require extra libs during execution. Now I cannot choose any libs for that job type To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1488218/+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 1300265] Re: some tests call assert_called_once() into a mock, this function doesn't exists, and gets auto-mocked, falsely passing tests
** Also affects: sahara Importance: Undecided 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/1300265 Title: some tests call assert_called_once() into a mock, this function doesn't exists, and gets auto-mocked, falsely passing tests Status in neutron: Fix Released Status in Sahara: New Bug description: neutron/tests/unit/agent/linux/test_async_process.py: spawn.assert_called_once() neutron/tests/unit/agent/linux/test_async_process.py: func.assert_called_once() neutron/tests/unit/agent/linux/test_async_process.py: mock_start.assert_called_once() neutron/tests/unit/agent/linux/test_async_process.py: mock_kill_event.send.assert_called_once() neutron/tests/unit/agent/linux/test_async_process.py: mock_kill_process.assert_called_once(pid) neutron/tests/unit/test_dhcp_agent.py: log.error.assert_called_once() neutron/tests/unit/test_dhcp_agent.py: device.route.get_gateway.assert_called_once() neutron/tests/unit/test_dhcp_agent.py: device.route.get_gateway.assert_called_once() neutron/tests/unit/test_dhcp_agent.py: device.route.get_gateway.assert_called_once() neutron/tests/unit/test_dhcp_agent.py: device.route.get_gateway.assert_called_once() neutron/tests/unit/test_dhcp_agent.py: device.route.get_gateway.assert_called_once() neutron/tests/unit/test_dhcp_agent.py: device.route.get_gateway.assert_called_once() neutron/tests/unit/test_dhcp_agent.py: device.route.get_gateway.assert_called_once() neutron/tests/unit/test_post_mortem_debug.py: mock_post_mortem.assert_called_once() neutron/tests/unit/test_linux_interface.py: log.assert_called_once() neutron/tests/unit/test_l3_agent.py:self.send_arp.assert_called_once() neutron/tests/unit/test_l3_agent.py:self.send_arp.assert_called_once() neutron/tests/unit/test_l3_agent.py:self.send_arp.assert_called_once() neutron/tests/unit/test_l3_agent.py:self.send_arp.assert_called_once() neutron/tests/unit/test_l3_agent.py:self.send_arp.assert_called_once() neutron/tests/unit/cisco/test_nexus_plugin.py: mock_db.assert_called_once() neutron/tests/unit/linuxbridge/test_lb_neutron_agent.py: exec_fn.assert_called_once() neutron/tests/unit/services/firewall/agents/l3reference/test_firewall_l3_agent.py: mock_driver_update_firewall.assert_called_once( neutron/tests/unit/services/firewall/agents/l3reference/test_firewall_l3_agent.py: mock_driver_delete_firewall.assert_called_once( To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1300265/+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 1470826] [NEW] If action during handling BatchAction failed, then got Traceback in logs
Public bug reported: If during operation some action (for example, delete action) became failed, then got following traceback in logs: Traceback (most recent call last): File /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/logging/__init__.py, line 851, in emit msg = self.format(record) File /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/logging/__init__.py, line 724, in format return fmt.format(record) File /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/logging/__init__.py, line 464, in format record.message = record.getMessage() File /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/logging/__init__.py, line 328, in getMessage msg = msg % self.args TypeError: not all arguments converted during string formatting It happens because of following line: https://github.com/openstack/horizon/blob/master/horizon/tables/actions.py#L823 ** Affects: horizon Importance: Undecided Assignee: Vitaly Gridnev (vgridnev) Status: In Progress ** Changed in: horizon Assignee: (unassigned) = Vitaly Gridnev (vgridnev) -- 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/1470826 Title: If action during handling BatchAction failed, then got Traceback in logs Status in OpenStack Dashboard (Horizon): In Progress Bug description: If during operation some action (for example, delete action) became failed, then got following traceback in logs: Traceback (most recent call last): File /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/logging/__init__.py, line 851, in emit msg = self.format(record) File /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/logging/__init__.py, line 724, in format return fmt.format(record) File /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/logging/__init__.py, line 464, in format record.message = record.getMessage() File /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/logging/__init__.py, line 328, in getMessage msg = msg % self.args TypeError: not all arguments converted during string formatting It happens because of following line: https://github.com/openstack/horizon/blob/master/horizon/tables/actions.py#L823 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1470826/+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 1259292] Re: Some tests use assertEqual(observed, expected) , the argument order is wrong
** Also affects: sahara Importance: Undecided Status: New ** Changed in: sahara Status: New = 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/1259292 Title: Some tests use assertEqual(observed, expected) , the argument order is wrong Status in OpenStack Telemetry (Ceilometer): Invalid Status in Cinder: In Progress Status in Orchestration API (Heat): Fix Released Status in OpenStack Dashboard (Horizon): In Progress Status in Python client library for Ceilometer: In Progress Status in Python client library for Cinder: Fix Committed Status in OpenStack Data Processing (Sahara): Confirmed Bug description: The test cases will produce a confusing error message if the tests ever fail, so this is worth fixing. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1259292/+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
