[Yahoo-eng-team] [Bug 1713420] Re: event: subnet.create.* lacks detailed information
closing, as i assume nothing was done on neutron end. if there is, this is a trivial addition to event_definitions ** Changed in: ceilometer Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1713420 Title: event: subnet.create.* lacks detailed information Status in Ceilometer: Invalid Status in neutron: New Bug description: This is actually not a bug report but much like a feature request. I have found out that subnet.create.* events have such few traits recorded: project_id, user_id, request_id, resource_id, service. Information such as allocation_pools, cidr, dns_nameservers, etc., is not recorded, but they are quite essential in my opinion. I have done a little research and found that neutron doesn't store these traits either when it generates notifications. It might be my fault that I missed something. Glad if you would tell me that I did. I'm wondering if anyone like me thinks that this is a quite important feature to have. And I'm guessing there are not much works to be done if we decide to implement this. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1713420/+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 1699060] Re: Impossible to define policy rule based on domain ID
please don't create these openstack-wide bugs, it spams everyone. i've removed telemetry projects but feel free to apply patches to them (don't do it for ceilometer since it doesn't have an active api). ** No longer affects: aodh ** No longer affects: ceilometer ** No longer affects: panko -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1699060 Title: Impossible to define policy rule based on domain ID Status in Cinder: New Status in Glance: New Status in heat: New Status in Manila: New Status in Murano: New Status in neutron: New Status in OpenStack Compute (nova): New Status in watcher: New Bug description: We have common approach to set rules for each API using policy.json file. And for the moment, it is not possible to use "domain_id" in policy rules, only "project_id" and "user_id". It becomes very important because Keystone API v3 is used more and more. The only service that supports rules with "domain_id" is Keystone itself. As a result we should be able to use following rules: "admin_or_domain_owner": "is_admin:True or domain_id:%(domain_id)s", "domain_owner": "domain_id:%(domain_id)s", like this: "volume:get": "rule:domain_owner", or "volume:get": "rule:admin_or_domain_owner", Right now, we always get 403 error having such rules. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1699060/+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 1693670] Re: Fix doc generation for Python3
** No longer affects: panko ** No longer affects: aodh ** No longer affects: ceilometer ** No longer affects: oslo.messaging -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1693670 Title: Fix doc generation for Python3 Status in Barbican: Fix Released Status in Cue: In Progress Status in Designate: Fix Released Status in OpenStack Backup/Restore and DR (Freezer): In Progress Status in Glance: In Progress Status in glance_store: In Progress Status in ldappool: Fix Released Status in Meteos: In Progress Status in neutron: Fix Released Status in OpenStack Security Advisory: In Progress Status in python-heatclient: In Progress Status in python-senlinclient: In Progress Status in Python client library for Zaqar: In Progress Status in OpenStack Object Storage (swift): In Progress Status in tacker: Fix Released Status in tempest: In Progress Status in OpenStack DBaaS (Trove): In Progress Status in zaqar: Fix Released Status in Zun: Fix Released Bug description: Fix the Sphinx html_last_updated_fmt for Python3. The html_last_updated_fmt option is interpeted as a byte string in python3, causing Sphinx build to break. This patch makes it utf-8 string. To manage notifications about this bug go to: https://bugs.launchpad.net/barbican/+bug/1693670/+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 1590608] Re: Services should use http_proxy_to_wsgi middleware
** Changed in: gnocchi 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/1590608 Title: Services should use http_proxy_to_wsgi middleware Status in Aodh: Fix Released Status in Barbican: Fix Released Status in Ceilometer: Fix Released Status in Cinder: Fix Released Status in cloudkitty: Fix Committed Status in congress: New Status in Freezer: Fix Released Status in Glance: Fix Released Status in Gnocchi: Fix Released Status in heat: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in Magnum: Fix Released Status in neutron: Fix Released Status in Panko: Fix Released Status in Sahara: Fix Released Status in OpenStack Search (Searchlight): Fix Released Status in senlin: Fix Released Status in OpenStack DBaaS (Trove): Fix Released Bug description: It's a common problem when putting a service behind a load balancer to need to forward the Protocol and hosts of the original request so that the receiving service can construct URLs to the loadbalancer and not the private worker node. Most services have implemented some form of secure_proxy_ssl_header = HTTP_X_FORWARDED_PROTO handling however exactly how this is done is dependent on the service. oslo.middleware provides the http_proxy_to_wsgi middleware that handles these headers and the newer RFC7239 forwarding header and completely hides the problem from the service. This middleware should be adopted by all services in preference to their own HTTP_X_FORWARDED_PROTO handling. To manage notifications about this bug go to: https://bugs.launchpad.net/aodh/+bug/1590608/+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 1661262] Re: String interpolation should be handled by logger
please don't create generic bugs against multiple projects. launchpad
doesn't handle this well and it also spams a lot of projects with
unrelated updates. thanks :)
** No longer affects: python-ceilometerclient
--
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/1661262
Title:
String interpolation should be handled by logger
Status in OpenStack Dashboard (Horizon):
In Progress
Status in python-heatclient:
In Progress
Status in python-ironicclient:
In Progress
Status in python-neutronclient:
In Progress
Status in OpenStack Object Storage (swift):
Fix Released
Bug description:
According to [1] guideline, strings should be interpolated by the
logger.
# WRONG
LOG.info(_LI('some message: variable=%s') % variable)
# RIGHT
LOG.info(_LI('some message: variable=%s'), variable)
[1]:
http://docs.openstack.org/developer/oslo.i18n/guidelines.html#adding-variables-to-log-messages
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1661262/+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 1596829] Re: String interpolation should be delayed at logging calls
** No longer affects: ceilometer
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
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 heat:
New
Status in Ironic:
Fix Released
Status in masakari:
Fix Released
Status in networking-vsphere:
Fix Released
Status in neutron:
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-neutronclient:
Fix Released
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 1082248] Re: Use uuidutils instead of uuid.uuid4()
** No longer affects: gnocchi -- 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 Cinder: In Progress Status in OpenStack Dashboard (Horizon): Fix Released Status in Ironic: Fix Released Status in ironic-python-agent: Fix Released Status in Karbor: Fix Released Status in kolla: Fix Committed Status in kuryr: Fix Released Status in kuryr-libnetwork: Fix Released Status in Magnum: In Progress Status in Mistral: Fix Released Status in networking-calico: In Progress Status in networking-ovn: Fix Released Status in networking-sfc: In Progress Status in neutron: Fix Released Status in OpenStack Compute (nova): In Progress Status in python-muranoclient: In Progress Status in Sahara: Fix Released Status in senlin: Fix Released Status in tacker: In Progress Status in watcher: Fix Released 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/cinder/+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 1600788] Re: If a common message is not being used, they should each be treated separately with respect to choosing a marker function
** No longer affects: ceilometer
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1600788
Title:
If a common message is not being used, they should each be treated
separately with respect to choosing a marker function
Status in Glance:
Fix Released
Status in glance_store:
In Progress
Status in OpenStack Dashboard (Horizon):
New
Status in Magnum:
Fix Released
Status in neutron:
Triaged
Status in oslo.log:
Fix Released
Status in Solum:
New
Bug description:
Follow the
http://docs.openstack.org/developer/oslo.i18n/guidelines.html
For example, do not do this:
# WRONG
LOG.exception(_('There was an error.'))
raise LocalExceptionClass(_('An error occured.'))
Instead, use this style:
# RIGHT
LOG.exception(_LE('There was an error.'))
raise LocalExceptionClass(_('An error occured.'))
And oslo.log has the problem,we shuld correct it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1600788/+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 1600109] Re: Unit tests should not perform logging, but some tests still use
** No longer affects: ceilometer -- 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/1600109 Title: Unit tests should not perform logging,but some tests still use Status in Cinder: Invalid Status in Glance: Incomplete Status in OpenStack Identity (keystone): Won't Fix Status in Magnum: Incomplete Status in OpenStack Compute (nova): Invalid Status in python-cinderclient: Invalid Status in python-glanceclient: Incomplete Status in python-keystoneclient: Won't Fix Status in python-neutronclient: Incomplete Status in python-novaclient: Invalid Status in python-rackclient: Incomplete Status in python-swiftclient: Incomplete Status in rack: Incomplete Status in OpenStack Object Storage (swift): Incomplete Status in OpenStack DBaaS (Trove): Invalid Bug description: We shuld remove the logging To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1600109/+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 1517839] Re: Make CONF.set_override with parameter enforce_type=True by default
** No longer affects: ceilometer ** No longer affects: aodh -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1517839 Title: Make CONF.set_override with parameter enforce_type=True by default Status in Cinder: In Progress Status in cloudkitty: Fix Released Status in Designate: Fix Released Status in Freezer: In Progress Status in Glance: Invalid Status in glance_store: In Progress Status in heat: Fix Released Status in Ironic: Triaged Status in Karbor: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in kolla: New Status in Magnum: In Progress Status in Manila: Fix Released Status in Murano: Fix Released Status in neutron: Won't Fix Status in OpenStack Compute (nova): Fix Released Status in octavia: New Status in oslo.config: In Progress Status in oslo.messaging: Fix Released Status in Quark: Money Reinvented: New Status in Rally: Fix Released Status in senlin: Fix Released Status in tacker: In Progress Status in watcher: Fix Released Bug description: 1. Problems : oslo_config provides method CONF.set_override[1] , developers usually use it to change config option's value in tests. That's convenient . By default parameter enforce_type=False, it doesn't check any type or value of override. If set enforce_type=True , will check parameter override's type and value. In production code(running time code), oslo_config always checks config option's value. In short, we test and run code in different ways. so there's gap: config option with wrong type or invalid value can pass tests when parameter enforce_type = False in consuming projects. that means some invalid or wrong tests are in our code base. [1] https://github.com/openstack/oslo.config/blob/master/oslo_config/cfg.py#L2173 2. Proposal 1) Fix violations when enforce_type=True in each project. 2) Make method CONF.set_override with enforce_type=True by default in oslo_config You can find more details and comments in https://etherpad.openstack.org/p/enforce_type_true_by_default 3. How to find violations in your projects. 1. Run tox -e py27 2. then modify oslo.config with enforce_type=True cd .tox/py27/lib64/python2.7/site-packages/oslo_config edit cfg.py with enforce_type=True -def set_override(self, name, override, group=None, enforce_type=False): +def set_override(self, name, override, group=None, enforce_type=True): 3. Run tox -e py27 again, you will find violations. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1517839/+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 1564110] Re: OpenStack should support MySQL Cluster (NDB)
no one worked on ceilometer legacy storage for over a year. use gnocchi or something else ** Changed in: ceilometer Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1564110 Title: OpenStack should support MySQL Cluster (NDB) Status in Ceilometer: Won't Fix Status in Cinder: Opinion Status in Glance: New Status in heat: New Status in Ironic: Confirmed Status in OpenStack Identity (keystone): Incomplete Status in neutron: Incomplete Status in OpenStack Compute (nova): Confirmed Status in oslo.db: New Bug description: oslo.db assumes that a MySQL database can only have a storage engine of InnoDB. This causes complications for OpenStack to support other MySQL storage engines, such as MySQL Cluster (NDB). Oslo.db should have a configuration string (i.e. mysql_storage_engine) in the oslo_db database group that can be used by SQLalchemy, Alembic, and OpenStack to implement the desired support and behavior for alternative MySQL storage engines. I do have a change-set patch for options.py in oslo_db that will add this functionality. I'll post once I'm added to the CLA for OpenStack. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1564110/+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 1346778] Re: Neutron does not work by default without a keystone admin user
** Changed in: ceilometer Status: Incomplete => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1346778 Title: Neutron does not work by default without a keystone admin user Status in Ceilometer: Invalid Status in neutron: Expired Bug description: The default neutron policy.json 'context_is_admin' only matches on 'role:admin' and the account that neutron is configured with must match 'context_is_admin' for neutron to function correctly. This means that without modifying policy.json, a deployer cannot use a non-admin account for neutron. The policy.json keywords have no way to match the username of the neutron keystone credentials. This means that policy.json has to be modified for every deployment that doesn't use an admin user to match the keystone user neutron is configured with. This seems like an unnecessary burden to leave to deployers to achieve a secure deployment. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1346778/+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
** No longer affects: ceilometer
** No longer affects: aodh
--
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 1384379] Re: versions resource uses host_url which may be incorrect
** No longer affects: ceilometer -- 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/1384379 Title: versions resource uses host_url which may be incorrect Status in Cinder: Fix Released Status in Glance: Fix Released Status in Glance icehouse series: Triaged Status in Glance juno series: Triaged Status in heat: Triaged Status in Ironic: Fix Released Status in Manila: Fix Released Status in OpenStack Compute (nova): Fix Released Status in Trove: In Progress Bug description: The versions resource constructs the links by using host_url, but the glance api endpoint may be behind a proxy or ssl terminator. This means that host_url may be incorrect. It should have a config option to override host_url like the other services do when constructing versions links. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1384379/+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 1517839] Re: Make CONF.set_override with parameter enforce_type=True by default
** No longer affects: ceilometer ** No longer affects: gnocchi -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1517839 Title: Make CONF.set_override with parameter enforce_type=True by default Status in Cinder: In Progress Status in cloudkitty: Fix Released Status in Designate: Confirmed Status in heat: New Status in OpenStack Identity (keystone): Fix Released Status in Manila: New Status in Murano: Fix Released Status in neutron: Won't Fix Status in oslo.config: New Status in oslo.messaging: Fix Released Status in Rally: Fix Released Status in watcher: Fix Released Bug description: 1. Problems : oslo_config provides method CONF.set_override[1] , developers usually use it to change config option's value in tests. That's convenient . By default parameter enforce_type=False, it doesn't check any type or value of override. If set enforce_type=True , will check parameter override's type and value. In production code(running time code), oslo_config always checks config option's value. In short, we test and run code in different ways. so there's gap: config option with wrong type or invalid value can pass tests when parameter enforce_type = False in consuming projects. that means some invalid or wrong tests are in our code base. There is nova POC result when I enable "enforce_type=true" [2], and I must fix them in [3] [1] https://github.com/openstack/oslo.config/blob/master/oslo_config/cfg.py#L2173 [2] http://logs.openstack.org/16/242416/1/check/gate-nova-python27/97b5eff/testr_results.html.gz [3] https://review.openstack.org/#/c/242416/ https://review.openstack.org/#/c/242717/ https://review.openstack.org/#/c/243061/ 2. Proposal 1) Make method CONF.set_override with enforce_type=True in consuming projects. and fix violations when enforce_type=True in each project. 2) Make method CONF.set_override with enforce_type=True by default in oslo_config Hope some one from consuming projects can help make enforce_type=True in consuming projects and fix violations, You can find more details and comments in https://etherpad.openstack.org/p/enforce_type_true_by_default To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1517839/+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: ceilometer ** No longer affects: python-ceilometerclient -- 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: In Progress 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 Sahara: 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 1523716] Re: oslo.utils upgrade breaks unit tests
** Changed in: ceilometer Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1523716 Title: oslo.utils upgrade breaks unit tests Status in Ceilometer: Invalid Status in Magnum: New Status in networking-odl: New Status in neutron: New Status in oslo.utils: Fix Released Bug description: Upgraded oslo.utils (3.1.0) is breaking ceilometer unit tests: https://jenkins07.openstack.org/job/gate-ceilometer- python34/897/console Stack Trace: 2015-12-07 20:17:19.296 | __import__(module_str) 2015-12-07 20:17:19.296 | File "ceilometer/notification.py", line 24, in 2015-12-07 20:17:19.296 | from ceilometer import coordination 2015-12-07 20:17:19.296 | File "ceilometer/coordination.py", line 20, in 2015-12-07 20:17:19.297 | import tooz.coordination 2015-12-07 20:17:19.297 | File "/home/jenkins/workspace/gate-ceilometer-python27/.tox/py27/local/lib/python2.7/site-packages/tooz/coordination.py", line 21, in 2015-12-07 20:17:19.297 | from oslo_utils import netutils 2015-12-07 20:17:19.297 | File "/home/jenkins/workspace/gate-ceilometer-python27/.tox/py27/local/lib/python2.7/site-packages/oslo_utils/netutils.py", line 25, in 2015-12-07 20:17:19.297 | import netifaces 2015-12-07 20:17:19.297 | ImportError: No module named netifaces To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1523716/+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 1351846] Re: notification image.update/image.upload meter does not works with qpid
marking invalid as qpid support in oslo.messaging is poor. i think this should be reopend against oslo.messaging if anything ** Changed in: ceilometer Status: Incomplete => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1351846 Title: notification image.update/image.upload meter does not works with qpid Status in Ceilometer: Invalid Status in Glance: New Bug description: The following tempest test fails when I select 'qpid' instead of 'rabbit' ENABLED_SERVICES in the devstack local.conf: tempest.api.telemetry.test_telemetry_notification_api.TelemetryNotificationAPITestXML.test_check_glance_v1_notifications[gate,image,smoke] tempest.api.telemetry.test_telemetry_notification_api.TelemetryNotificationAPITestXML.test_check_glance_v2_notifications[gate,image,smoke] tempest.api.telemetry.test_telemetry_notification_api.TelemetryNotificationAPITestJSON.test_check_glance_v1_notifications[gate,image,smoke] tempest.api.telemetry.test_telemetry_notification_api.TelemetryNotificationAPITestJSON.test_check_glance_v2_notifications[gate,image,smoke] https://github.com/openstack/tempest/blob/master/tempest/api/telemetry/test_telemetry_notification_api.py After a $ glance image-create --file /etc/passwd --name passwd --container-format bare --disk-format raw the $ ceilometer meter-list does not shows 'image.update' or 'image.upload' meter. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1351846/+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
** Changed in: python-ceilometerclient Status: In Progress => Invalid ** Changed in: python-ceilometerclient Assignee: Jia Dong (jiadong-jia) => (unassigned) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1259292 Title: Some tests use assertEqual(observed, expected) , the argument order is wrong Status in Ceilometer: Invalid Status in Cinder: Fix Released Status in Glance: New Status in heat: Fix Released Status in OpenStack Dashboard (Horizon): In Progress Status in Keystone: Triaged Status in Manila: In Progress Status in neutron: New Status in OpenStack Compute (nova): In Progress Status in python-ceilometerclient: Invalid Status in python-cinderclient: Fix Released Status in Sahara: Fix Released 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
[Yahoo-eng-team] [Bug 1396677] Re: Heavy use of metering labels/rules cause memory leak in neutron server
** Changed in: ceilometer Status: Incomplete = Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1396677 Title: Heavy use of metering labels/rules cause memory leak in neutron server Status in Ceilometer: Invalid Status in neutron: New Bug description: We found that large amount of metering labels and rules cause memory leak in neutron server. This problem is multiplied by amount of workers (10 workers - 10x memory leak). In our case we have 657 metering-lables and 122399 metering-label- rules, If anyone query them, neutron-server (worker) picked request eats +400Mb of memory and keep it until restart. If more requests send, they come to different workers cause each of them to bloat up. Same problem happens if neutron-plugin-metering-agent running (it send requests to neutron-server with same effect). If neutron-server hit 100% CPU it starts to consume even more memory (in our case up to 1.4Gb per neutron-server worker). To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1396677/+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 1188218] Re: Support standard ceilometer compute metrics with nova baremetal
https://github.com/openstack/ceilometer/commit/683ead74af36c88575ca8bce312ecf1428a5cc80 ** Changed in: ceilometer Status: Triaged = Fix Released ** Changed in: ceilometer Assignee: (unassigned) = Zhai, Edwin (edwin-zhai) -- 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/1188218 Title: Support standard ceilometer compute metrics with nova baremetal Status in OpenStack Telemetry (Ceilometer): Fix Released Status in OpenStack Bare Metal Provisioning Service (Ironic): Fix Released Status in OpenStack Compute (Nova): Won't Fix Status in tripleo - openstack on openstack: Triaged Bug description: I guess this is a subset of bug #1004468 and https://blueprints.launchpad.net/ceilometer/+spec/non-libvirt-hw However, it's a bit different for nova-baremetal. There is no hypervisor we can query for CPU, disk and network statistics so we can't just add another plugin for ceilometer's compute agent. Instead, we will need an agent which runs inside each baremetal instance and posts samples to ceilometer's public /meters/ API At a first glance, these look like the counters which require a guest agent: cpu CPU time used cpu_util CPU utilisation disk.read.requestNumber of read requests disk.write.request Number of write requests disk.read.bytes Volume of read in B disk.write.bytes Volume of write in B network.incoming.bytes number of incoming bytes on the network network.outgoing.bytes number of outgoing bytes on the network network.incoming.packets number of incoming packets network.outgoing.packets number of outgoing packets For the other compute counters, we can add baremetal support to the ceilometer compute agent - e.g. these counters: instance Duration of instance instance:type Duration of instance type (openstack types) memory Volume of RAM in MB cpus Number of VCPUs disk.root.size Size of root disk in GB disk.ephemeral.size Size of ephemeral disk in GB One thing to consider is access control to these counters - we probably don't usually allow tenants to update these counters in, but in this case the tenant will require that ability. It's unclear whether this guest agent would live in ceilometer, nova baremetal or ironic. It's interfacing with (what should be) a very stable ceilometer API, so there's no particular need for it to live in ceilometer. I'm also adding a tripleo task, since I expect tripleo will want these metrics available for things like auto-scaling or simply resource monitoring. We'd need at least a diskimage-builder element which includes the guest agent. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1188218/+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 1320617] Re: [Image] failed to reach ACTIVE status within the required time (196 s). Current status: SAVING
marking this invalid from ceilometer pov, since this hasn't cropped up. as eglynn mentioned, there were various changes to address issues... not really sure if consuming 7.5% cpu is the root of issue regardless. ** Changed in: ceilometer Status: Incomplete = 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/1320617 Title: [Image] failed to reach ACTIVE status within the required time (196 s). Current status: SAVING Status in OpenStack Telemetry (Ceilometer): Invalid Status in OpenStack Compute (Nova): Invalid Bug description: http://logs.openstack.org/08/92608/1/gate/gate-tempest-dsvm-postgres- full/57b137a/console.html.gz The relevant part of the test case: 1. Boot servet1 2. Boot server2 wait until active 3. wait until server1 ACTIVE 4. Create snapshot from server1, wait until ACTIVE with 196 sec timeout 5. Cleanup, die with the first failure Normally the test case would create 2 additional image at the beginning, but now died at fist image creation. 2014-05-09 21:44:09.857 | Captured traceback: 2014-05-09 21:44:09.858 | ~~~ 2014-05-09 21:44:09.858 | Traceback (most recent call last): 2014-05-09 21:44:09.858 | File tempest/api/compute/images/test_list_image_filters.py, line 45, in setUpClass 2014-05-09 21:44:09.858 | cls.server1['id'], wait_until='ACTIVE') 2014-05-09 21:44:09.858 | File tempest/api/compute/base.py, line 302, in create_image_from_server 2014-05-09 21:44:09.858 | kwargs['wait_until']) 2014-05-09 21:44:09.858 | File tempest/services/compute/xml/images_client.py, line 140, in wait_for_image_status 2014-05-09 21:44:09.858 | waiters.wait_for_image_status(self, image_id, status) 2014-05-09 21:44:09.858 | File tempest/common/waiters.py, line 129, in wait_for_image_status 2014-05-09 21:44:09.858 | raise exceptions.TimeoutException(message) 2014-05-09 21:44:09.859 | TimeoutException: Request timed out 2014-05-09 21:44:09.859 | Details: (ListImageFiltersTestXML:setUpClass) Image 20b6e7a9-f65d-4d17-b025-59f9237ff8cb failed to reach ACTIVE status within the required time (196 s). Current status: SAVING. logstash: http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiZmFpbGVkIHRvIHJlYWNoIEFDVElWRSBzdGF0dXMgd2l0aGluIHRoZSByZXF1aXJlZCB0aW1lXCIgQU5EIGZpbGVuYW1lOlwiY29uc29sZS5odG1sXCIgQU5EIG1lc3NhZ2U6XCJDdXJyZW50IHN0YXR1czogU0FWSU5HXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6ImFsbCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjE0MDA0MTEyNDcwMzksIm1vZGUiOiIiLCJhbmFseXplX2ZpZWxkIjoiIn0= message:failed to reach ACTIVE status within the required time AND filename:console.html AND message:Current status: SAVING To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1320617/+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 1221987] Re: compute node heartbeat out of sync causing scheduler to fail in devstack: VMs fail to spawn
marking this as won't fix on ceilometer end. we removed the nova_notifier as the plugin mechanism didn't play well with nova ** Changed in: ceilometer Status: Triaged = Won't Fix -- 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/1221987 Title: compute node heartbeat out of sync causing scheduler to fail in devstack: VMs fail to spawn Status in OpenStack Telemetry (Ceilometer): Won't Fix Status in OpenStack Compute (Nova): Fix Released Bug description: I have now seen this several times in devstack-gate Occasionally instances will go into error state, and when checking the logs, I see the error is in nova-scheduler where the heartbeat is too old, which causes the scheduler to not schedule on that node. http://logs.openstack.org/97/45497/2/check/gate-tempest-devstack-vm-postgres-full/084442d/logs/screen-n-sch.txt.gz#_2013-09-07_00_06_14_880 From logfile: DB_Driver.is_up last_heartbeat = 2013-09-07 00:04:47.516557 elapsed = 87.363841 is_up /opt/stack/new/nova/nova/servicegroup/drivers/db.py:71 (devstack-precise-hpcloud-az1-229926, devstack-precise-hpcloud-az1-229926) ram:5170 disk:210944 io_ops:5 instances:18 is disabled or has not been heard from in a while host_passes /opt/stack/new/nova/nova/scheduler/filters/compute_filter.py:44 Filter ComputeFilter returned 0 host(s) get_filtered_objects /opt/stack/new/nova/nova/filters.py:85 [instance: 415fb048-1d47-4fb8-8974-323529d8b1b5] Setting instance to ERROR state. 20 To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1221987/+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 1060985] Re: Notifications are lacking for the L3 API (router-interface add and remove)
completed here: https://github.com/openstack/ceilometer/commit/52eed63c656fc4d15d0ee7c528d39023b6204698 ** Changed in: ceilometer Status: In Progress = Fix Released ** Changed in: ceilometer Assignee: François Charlier (francois-charlier) = Julien Danjou (jdanjou) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1060985 Title: Notifications are lacking for the L3 API (router-interface add and remove) Status in OpenStack Telemetry (Ceilometer): Fix Released Status in OpenStack Neutron (virtual network service): Fix Released Bug description: Currently there ar no notifications for the L3 api, for example creation of a router. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1060985/+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 1424061] Re: keystone server should default to localhost-only
see sileht's comment: https://review.openstack.org/#/c/158523/ ** Changed in: ceilometer Assignee: Eric Brown (ericwb) = (unassigned) ** Changed in: ceilometer Status: In Progress = Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1424061 Title: keystone server should default to localhost-only Status in OpenStack Telemetry (Ceilometer): Won't Fix Status in OpenStack Identity (Keystone): Won't Fix Bug description: By default keystone will listen on all interfaces. Keystone should use secure defaults. In this case, listen on localhost-only by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1424061/+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 1428821] [NEW] n-api fails to start on juno grenade
Public bug reported: possibly related to this: https://github.com/openstack/nova/commit/a657582c5cd8a39580c44ad401fd3e69870068b1 grenade tests are not passing due to n-api not starting logs here: http://logs.openstack.org/56/161256/1/check/check-grenade- dsvm/6fb9bfa/logs/ from n-api log: 2015-03-05 14:04:34.874 10501 INFO nova.openstack.common.service [-] Started child 10508 Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py, line 346, in fire_timers timer() File /usr/lib/python2.7/dist-packages/eventlet/hubs/timer.py, line 56, in __call__ cb(*args, **kw) File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 194, in main result = function(*args, **kwargs) TypeError: server() got an unexpected keyword argument 'socket_timeout' 2015-03-05 14:04:34.876 10501 INFO nova.openstack.common.service [-] Started child 10509 Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py, line 346, in fire_timers timer() File /usr/lib/python2.7/dist-packages/eventlet/hubs/timer.py, line 56, in __call__ cb(*args, **kw) File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 194, in main result = function(*args, **kwargs) TypeError: server() got an unexpected keyword argument 'socket_timeout' 2015-03-05 14:04:34.878 10501 INFO nova.openstack.common.service [-] Started child 10510 Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py, line 346, in fire_timers timer() File /usr/lib/python2.7/dist-packages/eventlet/hubs/timer.py, line 56, in __call__ cb(*args, **kw) File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 194, in main result = function(*args, **kwargs) TypeError: server() got an unexpected keyword argument 'socket_timeout' ** Affects: nova Importance: Undecided Status: New -- 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/1428821 Title: n-api fails to start on juno grenade Status in OpenStack Compute (Nova): New Bug description: possibly related to this: https://github.com/openstack/nova/commit/a657582c5cd8a39580c44ad401fd3e69870068b1 grenade tests are not passing due to n-api not starting logs here: http://logs.openstack.org/56/161256/1/check/check-grenade- dsvm/6fb9bfa/logs/ from n-api log: 2015-03-05 14:04:34.874 10501 INFO nova.openstack.common.service [-] Started child 10508 Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py, line 346, in fire_timers timer() File /usr/lib/python2.7/dist-packages/eventlet/hubs/timer.py, line 56, in __call__ cb(*args, **kw) File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 194, in main result = function(*args, **kwargs) TypeError: server() got an unexpected keyword argument 'socket_timeout' 2015-03-05 14:04:34.876 10501 INFO nova.openstack.common.service [-] Started child 10509 Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py, line 346, in fire_timers timer() File /usr/lib/python2.7/dist-packages/eventlet/hubs/timer.py, line 56, in __call__ cb(*args, **kw) File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 194, in main result = function(*args, **kwargs) TypeError: server() got an unexpected keyword argument 'socket_timeout' 2015-03-05 14:04:34.878 10501 INFO nova.openstack.common.service [-] Started child 10510 Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py, line 346, in fire_timers timer() File /usr/lib/python2.7/dist-packages/eventlet/hubs/timer.py, line 56, in __call__ cb(*args, **kw) File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 194, in main result = function(*args, **kwargs) TypeError: server() got an unexpected keyword argument 'socket_timeout' To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1428821/+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 1257295] Re: openstack is full of misspelled words
marking this as invalid as it's too difficult to track and we've had various patches related to spelling since this bug. ** Changed in: ceilometer Status: In Progress = Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1257295 Title: openstack is full of misspelled words Status in OpenStack Telemetry (Ceilometer): Invalid Status in Designate: Fix Released Status in OpenStack Neutron (virtual network service): Fix Released Status in OpenStack Compute (Nova): Fix Released Status in The Oslo library incubator: Fix Released Status in Python Build Reasonableness: Fix Committed Status in Designate Client: Fix Released Status in Python client library for Nova: Fix Released Bug description: List of known misspellings http://paste.openstack.org/show/54354 Generated with: pip install misspellings git ls-files | grep -v locale | misspellings -f - To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1257295/+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 1222900] Re: verbose logging with standard devstack settings
** Also affects: devstack Importance: Undecided Status: New ** Changed in: horizon Status: Confirmed = Invalid ** Changed in: devstack Status: New = 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/1222900 Title: verbose logging with standard devstack settings Status in devstack - openstack dev environments: In Progress Status in OpenStack Dashboard (Horizon): Invalid Bug description: using a standard devstack setup, there seems to be a lot of (invalid) error logging. not sure if it is expected behaviour but it visually seems odd that it logs with [error] on every call yet the response seems to be ok: [Mon Sep 09 16:01:26 2013] [error] DEBUG:ceilometerclient.common.http: [Mon Sep 09 16:01:26 2013] [error] HTTP/1.0 200 OK [Mon Sep 09 16:01:26 2013] [error] date: Mon, 09 Sep 2013 16:01:26 GMT [Mon Sep 09 16:01:26 2013] [error] content-length: 2 [Mon Sep 09 16:01:26 2013] [error] content-type: application/json; charset=UTF-8 [Mon Sep 09 16:01:26 2013] [error] server: WSGIServer/0.1 Python/2.7.3 [Mon Sep 09 16:01:26 2013] [error] [Mon Sep 09 16:01:26 2013] [error] [] [Mon Sep 09 16:01:26 2013] [error] [Mon Sep 09 16:01:26 2013] [error] DEBUG:ceilometerclient.common.http:curl -i -X GET -H 'X-Auth-Token: 4ccec28a944671cf9d1246de45084742' -H 'Content-Type: application/json' -H 'Accept: application/json' -H 'User-Agent: python-ceilometerclient' http://10.0.2.15:8777/v2/meters/disk.read.requests/statistics?q.op=eqq.op=geq.op=leq.value=55cae1bb63dd491ca7504624c413a3c2q.value=2013-08-10+16%3A01%3A20.911959q.value=2013-09-09+16%3A01%3A20.911972q.field=project_idq.field=timestampq.field=timestamp [Mon Sep 09 16:01:26 2013] [error] DEBUG:ceilometerclient.common.http: [Mon Sep 09 16:01:26 2013] [error] HTTP/1.0 200 OK [Mon Sep 09 16:01:26 2013] [error] date: Mon, 09 Sep 2013 16:01:26 GMT [Mon Sep 09 16:01:26 2013] [error] content-length: 2 [Mon Sep 09 16:01:26 2013] [error] content-type: application/json; charset=UTF-8 [Mon Sep 09 16:01:26 2013] [error] server: WSGIServer/0.1 Python/2.7.3 [Mon Sep 09 16:01:26 2013] [error] [Mon Sep 09 16:01:26 2013] [error] [] [Mon Sep 09 16:01:26 2013] [error] [Mon Sep 09 16:01:26 2013] [error] DEBUG:ceilometerclient.common.http:curl -i -X GET -H 'X-Auth-Token: 4ccec28a944671cf9d1246de45084742' -H 'Content-Type: application/json' -H 'Accept: application/json' -H 'User-Agent: python-ceilometerclient' http://10.0.2.15:8777/v2/meters/disk.write.bytes/statistics?q.op=eqq.op=geq.op=leq.value=55cae1bb63dd491ca7504624c413a3c2q.value=2013-08-10+16%3A01%3A20.911959q.value=2013-09-09+16%3A01%3A20.911972q.field=project_idq.field=timestampq.field=timestamp To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1222900/+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 1368490] Re: oslo.middleware.sizelimit configuration conflict
** Changed in: oslo.middleware 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/1368490 Title: oslo.middleware.sizelimit configuration conflict Status in OpenStack Identity (Keystone): Invalid Status in Oslo WSGI middleware library: Fix Released Bug description: If the oslo.middleware package is installed in a keystone installation and any of the middleware in it included in keystone's pipeline then the application will error with a configuration conflict due to oslo.middleware.sizelimit adding the configuration option max_request_body_size which is already added by the keystone middleware RequestBodySizeLimiter. This ultimately blocks keystone from using oslo.middleware. Whether it's a bug in oslo or in keystone is debatable, but the bug had to be filed somewhere :) To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1368490/+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 1256043] Re: Need to add Development environment files to ignore list
we've decide in ceilometer to let users configure own gitignore for such cases... closing ceilo items. ** No longer affects: python-ceilometerclient ** No longer affects: ceilometer -- 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/1256043 Title: Need to add Development environment files to ignore list Status in OpenStack Dashboard (Horizon): In Progress Status in OpenStack Neutron (virtual network service): In Progress Status in Python client library for Cinder: Fix Committed Status in Python client library for Glance: In Progress Status in Python client library for Keystone: Fix Released Status in Python client library for Neutron: In Progress Status in Python client library for Nova: Fix Released Status in Python client library for Swift: Won't Fix Status in OpenStack Object Storage (Swift): Won't Fix Bug description: Following files generated by Eclipse development environment should be in ignore list to avoid their inclusion during a git push. .project .pydevproject To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1256043/+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 1348818] Re: Unittests do not succeed with random PYTHONHASHSEED value
** Also affects: wsme 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/1348818 Title: Unittests do not succeed with random PYTHONHASHSEED value Status in OpenStack Key Management (Barbican): Confirmed Status in OpenStack Telemetry (Ceilometer): Fix Committed Status in Cinder: In Progress Status in Designate: In Progress Status in OpenStack Image Registry and Delivery Service (Glance): In Progress Status in Orchestration API (Heat): In Progress Status in OpenStack Dashboard (Horizon): In Progress Status in OpenStack Bare Metal Provisioning Service (Ironic): Fix Committed Status in OpenStack Identity (Keystone): In Progress Status in OpenStack Neutron (virtual network service): In Progress Status in OpenStack Compute (Nova): New Status in Python client library for Neutron: In Progress Status in OpenStack Data Processing (Sahara, ex. Savanna): In Progress Status in Web Services Made Easy: New Bug description: New tox and python3.3 set a random PYTHONHASHSEED value by default. These projects should support this in their unittests so that we do not have to override the PYTHONHASHSEED value and potentially let bugs into these projects. To reproduce these failures: # install latest tox pip install --upgrade tox tox --version # should report 1.7.2 or greater cd $PROJECT_REPO # edit tox.ini to remove any PYTHONHASHSEED=0 lines tox -epy27 Most of these failures appear to be related to dict entry ordering. To manage notifications about this bug go to: https://bugs.launchpad.net/barbican/+bug/1348818/+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 1324218] Re: Empty Daily Report Page
** 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/1324218 Title: Empty Daily Report Page Status in OpenStack Telemetry (Ceilometer): New Status in OpenStack Dashboard (Horizon): New Bug description: Is the Daily Report tab implemented yet? OpenStack Icehouse on CentOS 6.5 (2.6.32-431.11.2.el6.x86_64 #1 SMP) I can see and select both resource usage tabs, however the Daily Report page is empty (for over 2 weeks) I see no errors in apache, keystone or ceilometer logs on the cloud controller node. On the compute nodes, I see many of these: 2014-05-27 09:17:21.625 18382 WARNING ceilometer.transformer.conversions [-] dropping sample with no predecessor: (ceilometer.sample.Sample object at 0x24ce810,) Here are package versions of relevant RPMs on the controller node: = Name: openstack-ceilometer-collector Relocations: (not relocatable) Version : 2014.1Vendor: Fedora Project Release : 2.el6 Build Date: Wed 07 May 2014 11:33:07 AM PDT Install Date: Mon 12 May 2014 06:07:35 PM PDT Build Host: buildvm-16.phx2.fedoraproject.org Name: openstack-ceilometer-api Relocations: (not relocatable) Version : 2014.1Vendor: Fedora Project Release : 2.el6 Build Date: Wed 07 May 2014 11:33:07 AM PDT Install Date: Mon 12 May 2014 06:07:35 PM PDT Build Host: buildvm-16.phx2.fedoraproject.org Name: python-ceilometerclient Relocations: (not relocatable) Version : 1.0.8 Vendor: Fedora Project Release : 1.el6 Build Date: Mon 16 Dec 2013 11:20:29 AM PST Install Date: Mon 05 May 2014 12:23:26 PM PDT Build Host: buildvm-25.phx2.fedoraproject.org Name: openstack-ceilometer-notification Relocations: (not relocatable) Version : 2014.1Vendor: Fedora Project Release : 2.el6 Build Date: Wed 07 May 2014 11:33:07 AM PDT Install Date: Mon 12 May 2014 06:07:26 PM PDT Build Host: buildvm-16.phx2.fedoraproject.org Name: openstack-ceilometer-central Relocations: (not relocatable) Version : 2014.1Vendor: Fedora Project Release : 2.el6 Build Date: Wed 07 May 2014 11:33:07 AM PDT Install Date: Mon 12 May 2014 06:07:35 PM PDT Build Host: buildvm-16.phx2.fedoraproject.org Name: openstack-ceilometer-common Relocations: (not relocatable) Version : 2014.1Vendor: Fedora Project Release : 2.el6 Build Date: Wed 07 May 2014 11:33:07 AM PDT Install Date: Mon 12 May 2014 06:07:26 PM PDT Build Host: buildvm-16.phx2.fedoraproject.org Name: openstack-ceilometer-alarm Relocations: (not relocatable) Version : 2014.1Vendor: Fedora Project Release : 2.el6 Build Date: Wed 07 May 2014 11:33:07 AM PDT Install Date: Mon 12 May 2014 06:07:35 PM PDT Build Host: buildvm-16.phx2.fedoraproject.org Name: python-ceilometerRelocations: (not relocatable) Version : 2014.1Vendor: Fedora Project Release : 2.el6 Build Date: Wed 07 May 2014 11:33:07 AM PDT Install Date: Mon 12 May 2014 06:07:26 PM PDT Build Host: buildvm-16.phx2.fedoraproject.org Name: mongodb Relocations: (not relocatable) Version : 2.4.6 Vendor: Fedora Project Release : 1.el6 Build Date: Thu 19 Sep 2013 12:24:03 PM PDT Install Date: Mon 05 May 2014 05:45:00 PM PDT Build Host: buildvm-09.phx2.fedoraproject.org = Relevant RPMs on the compute nodes: = Name: python-ceilometerRelocations: (not relocatable) Version : 2014.1Vendor: Fedora Project Release : 2.el6 Build Date: Wed 07 May 2014 11:33:07 AM PDT Install Date: Mon 12 May 2014 09:47:30 AM PDT Build Host: buildvm-16.phx2.fedoraproject.org Name: python-ceilometerclient Relocations: (not relocatable) Version : 1.0.8 Vendor: Fedora Project Release : 1.el6 Build Date: Mon 16 Dec 2013 11:20:29 AM PST Install Date: Mon 12 May 2014 09:47:28 AM PDT Build Host: buildvm-25.phx2.fedoraproject.org Name: openstack-ceilometer-common Relocations: (not relocatable) Version : 2014.1
[Yahoo-eng-team] [Bug 1321080] Re: auth token is exposed in meter http.request
** Also affects: neutron
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/1321080
Title:
auth token is exposed in meter http.request
Status in OpenStack Telemetry (Ceilometer):
New
Status in OpenStack Neutron (virtual network service):
In Progress
Status in Oslo - a Library of Common OpenStack Code:
Fix Committed
Status in OpenStack Security Advisories:
Incomplete
Status in pyCADF:
In Progress
Bug description:
auth token is exposed in meter http.request
# curl -i -X GET -H 'X-Auth-Token: 258ab6539b3b4eae8b3af307b8f5eadd'
-H 'Content-Type: application/json' -H 'Accept: application/json' -H
'User-Agent: python-ceilometerclient'
http://0.0.0.0:8777/v2/meters/http.request
---
snip..
{counter_name: http.request, user_id: 0, resource_id:
ip-9-37-74-33:8774, timestamp: 2014-05-16T17:42:16.851000, recorded_at:
2014-05-16T17:42:17.039000, resource_metadata:
{request.CADF_EVENT:initiator:host:address: 9.44.143.6,
request.CADF_EVENT:initiator:credential:token: 4724 8478,
request.RAW_PATH_INFO:
/v2/9af97e383dad44969bd650ebd55edfe0/servers/060c76a5-0031-430d-aa1e-01f9b3db234b,
request.REQUEST_METHOD: DELETE, event_type: http.request,
request.HTTP_X_TENANT_ID: 9af97e383dad44969bd650ebd55edfe0,
request.CADF_EVENT:typeURI: http://schemas.dmtf.org/cloud/audit/1.0/event;,
request.HTTP_X_PROJECT_NAME: ibm-default, host: nova-api,
request.SERVER_PORT: 8774, request.REMOTE_PORT: 55258,
request.HTTP_X_USER_ID: 0, request.HTTP_X_AUTH_TOKEN:
4724d3dd6b984079a58eecf406298478, request.CADF_EVENT:action: delete,
request.CADF_EVENT:target:typeURI: service/compute/servers/server,
request.HTTP_US
ER_AGENT: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101
Firefox/24.0,
snip...
auth token is masked in request.CADF_EVENT:initiator:credential:token:
4724 8478.
But it is exposed in request.HTTP_X_AUTH_TOKEN:
4724d3dd6b984079a58eecf406298478
To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1321080/+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 1280327] Re: notifier middleware broken by oslo.messaging
middleware moved to pycadf: https://review.openstack.org/#/c/73452/ clean up pycadf middleware in nova: https://review.openstack.org/#/c/75426/ ** Changed in: nova Status: In Progress = Fix Committed ** Changed in: pycadf Status: In Progress = 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/1280327 Title: notifier middleware broken by oslo.messaging Status in OpenStack Compute (Nova): Fix Committed Status in pyCADF: Fix Released Bug description: the audit and notifier middlewares in openstack.common.middleware are broken due to switch to oslo.messaging. the notifier middleware is in process of being graduated to oslo.messaging. the audit middleware will be graduated to pyCADF library. incoming fix is to drop common code as it only works again openstack.common.notifier system. instead the audit and notifier middlewares will work against pyCADF and oslo.messaging libraries respectively. both libraries are currently part of Nova already. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1280327/+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 1280327] [NEW] notifier middleware broken by oslo.messaging
Public bug reported: the audit and notifier middlewares in openstack.common.middleware are broken due to switch to oslo.messaging. the notifier middleware is in process of being graduated to oslo.messaging as well. the audit middleware will be graduated to pyCADF library. incoming fix is to drop common code as it only works again openstack.common.notifier system. instead the audit and notifier middlewares will work against pyCADF and oslo.messaging libraries respectively. both libraries are currently part of Nova already. ** Affects: nova Importance: Undecided Assignee: gordon chung (chungg) Status: In Progress ** Affects: pycadf Importance: High Assignee: gordon chung (chungg) Status: In Progress ** Changed in: nova Status: New = In Progress ** Changed in: nova Assignee: (unassigned) = gordon chung (chungg) ** Also affects: pycadf Importance: Undecided Status: New ** Changed in: pycadf Status: New = In Progress ** Changed in: pycadf Importance: Undecided = Critical ** Changed in: pycadf Importance: Critical = High ** Changed in: pycadf Assignee: (unassigned) = gordon chung (chungg) -- 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/1280327 Title: notifier middleware broken by oslo.messaging Status in OpenStack Compute (Nova): In Progress Status in pyCADF: In Progress Bug description: the audit and notifier middlewares in openstack.common.middleware are broken due to switch to oslo.messaging. the notifier middleware is in process of being graduated to oslo.messaging as well. the audit middleware will be graduated to pyCADF library. incoming fix is to drop common code as it only works again openstack.common.notifier system. instead the audit and notifier middlewares will work against pyCADF and oslo.messaging libraries respectively. both libraries are currently part of Nova already. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1280327/+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 988698] Re: Tenant is created successfully without any information supplied.
fix was released in folsom for v2 api. name was set as required field.
see:
https://github.com/openstack/keystone/commit/19b6076869f6e177febc559b191f4ef9c352e55b
** Changed in: keystone
Status: Triaged = Fix Released
** Changed in: keystone
Assignee: adapaka bhavaniprasad (adapaka-prasad) = (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/988698
Title:
Tenant is created successfully without any information supplied.
Status in OpenStack Identity (Keystone):
Fix Released
Bug description:
In python keystoneclient ,when you call the create method of
TenantManager,you can set both tenant_name and description as None,the
tenant will be created successfully .The data of the new tenant looks
boring and meaningless.
Tenant {u'id': u'1bc61fe59518464bba2c1a37c6b9c76f', u'enabled': True,
u'description': None, u'name': None}
I suggest checking the type of tenant_name in
TenantManager.create(self, tenant_name, description=None,
enabled=True) method, and filtering the None type.
The same problem exists in UserManager.create(self, name, password,
email, tenant_id=None, enabled=True) method!
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/988698/+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
