[Bug 1554195] Re: Nova (juno) ignores logging_*_format_string in syslog output
Hello. We have our fix for this issue. See attachment. (It should be applied over ubuntu patchqueue). ** Patch added: "wz_fix_syslog_formatter.patch" https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1554195/+attachment/4601164/+files/wz_fix_syslog_formatter.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1554195 Title: Nova (juno) ignores logging_*_format_string in syslog output To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1554195/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1554195] [NEW] Nova (juno) ignores logging_*_format_string in syslog output
Public bug reported: Nova in juno ignores following settings in configuration file ([DEFAULT] section): logging_context_format_string logging_default_format_string logging_debug_format_suffix logging_exception_prefix when sending logs via syslog. Log entries on stderr / in log files are fine (use logging_*_format). Steps to reproduce: 1. set up custom logging stings and enable syslog: [DEFAULT] logging_default_format_string=MYSTYLE-DEFAULT-%(message)s logging_context_format_string=MYSTYLE-CONTEXT-%(message)s use_syslog=true 2. restart nova and perform some actions 3. Check the syslog content Expected behaviour: MYSTYLE- prefix in all messages. Actual behaviour: no changes in log message styles. This bug is specific to Juno version of nova. ** Affects: nova Importance: Undecided Status: New ** Affects: nova (Ubuntu) Importance: Undecided Status: New ** Also affects: nova (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1554195 Title: Nova (juno) ignores logging_*_format_string in syslog output To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1554195/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1385295] Re: use_syslog=True does not log to syslog via /dev/log anymore
Sorry, My bad. I didn't saw merge message. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-oslo.log in Ubuntu. https://bugs.launchpad.net/bugs/1385295 Title: use_syslog=True does not log to syslog via /dev/log anymore To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1385295/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1385295] Re: use_syslog=True does not log to syslog via /dev/log anymore
I think this patch is not merged to Juno https://review.openstack.org/#/c/202573/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-oslo.log in Ubuntu. https://bugs.launchpad.net/bugs/1385295 Title: use_syslog=True does not log to syslog via /dev/log anymore To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1385295/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1418590] Re: No ERROR state if image deleted, _base is lost and instance is rescued
Sorry, I've lost context of the fix, upstream is way to ahead. ** Changed in: nova Assignee: George Shuklin (george-shuklin) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1418590 Title: No ERROR state if image deleted, _base is lost and instance is rescued To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1418590/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1452312] Re: glance-registry process spins if rsyslog restarted with syslog logging enabled
@hopem, We've running on this (proposed) code for few weeks already, works fine. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-eventlet in Ubuntu. https://bugs.launchpad.net/bugs/1452312 Title: glance-registry process spins if rsyslog restarted with syslog logging enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-eventlet/+bug/1452312/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1452312] Re: glance-registry process spins if rsyslog restarted with syslog logging enabled
Hello. I can't see update nor in trusty-updates nor in trusty- updates/juno/main. It still contains 0.13.0-1ubuntu3.2~cloud0 instead of 0.13.0-1ubuntu3.3 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-eventlet in Ubuntu. https://bugs.launchpad.net/bugs/1452312 Title: glance-registry process spins if rsyslog restarted with syslog logging enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-eventlet/+bug/1452312/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1459726] Re: api servers hang with 100% CPU if syslog restarted
May be. I'm not sure. Anyway, this is not nova/glance/neutron bug, but python-eventlet, and it is mostly concerns for distributions, not for developers. ** Also affects: python-eventlet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-eventlet in Ubuntu. https://bugs.launchpad.net/bugs/1459726 Title: api servers hang with 100% CPU if syslog restarted To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1459726/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1458630] Re: broken package init-system-helpers: attempt to rewrite other package files
** Package changed: ubuntu => init-system-helpers (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1458630 Title: broken package init-system-helpers: attempt to rewrite other package files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1458630/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1418590] Re: No ERROR state if image deleted, _base is lost and instance is rescued
OK. I found some problems with my ideas: If instance have _base, it still can be rescued even if image is deleted. I'll think about this on second part. For now I'll set instance in ERROR if rescue was failed. (Bugreport says 'instance broken, but status is ACTIVE'). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1418590 Title: No ERROR state if image deleted, _base is lost and instance is rescued To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1418590/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1418590] Re: No ERROR state if image deleted, _base is lost and instance is rescued
Hello. We using qemu/kvm with raw disks. Normally, disk (qcow) will be irreversibly damaged if someone removes _base, but for the raw disks all stuff in _base is formality. We placing it on slow HDD raid0 (VS normal raid with SSD for instance disks), so losing HDD with _base's is normal case for us. In case of IO errors we're just replacing HDD, remounting _base, restarting nova-compute and continue to work without any problems. But 'rescue' has a problem (and I'm now in the process of Jenkins fight for fix). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1418590 Title: No ERROR state if image deleted, _base is lost and instance is rescued To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1418590/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1420953] [NEW] package python-oslo-serialization (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/python2.7/dist-packages/oslo/serialization/__init__.py', which is also in
Public bug reported: Preparing to unpack .../python-oslo.serialization_1.2.0-0ubuntu1_all.deb ... E: namespace:121: cannot remove /usr/lib/python2.7/dist-packages/oslo/__init__.py ProblemType: Package DistroRelease: Ubuntu 15.04 Package: python-oslo-serialization (not installed) ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4 Uname: Linux 3.18.0-12-generic i686 ApportVersion: 2.16-0ubuntu1 Architecture: i386 Date: Wed Feb 11 22:26:10 2015 DuplicateSignature: package:python-oslo-serialization:(not installed):trying to overwrite '/usr/lib/python2.7/dist-packages/oslo/serialization/__init__.py', which is also in package python-oslo.serialization 1.1.0-0ubuntu1 ErrorMessage: trying to overwrite '/usr/lib/python2.7/dist-packages/oslo/serialization/__init__.py', which is also in package python-oslo.serialization 1.1.0-0ubuntu1 InstallationDate: Installed on 2013-07-19 (572 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1) SourcePackage: python-oslo.serialization Title: package python-oslo-serialization (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/python2.7/dist-packages/oslo/serialization/__init__.py', which is also in package python-oslo.serialization 1.1.0-0ubuntu1 UpgradeStatus: Upgraded to vivid on 2014-09-26 (138 days ago) ** Affects: python-oslo.serialization (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 package-conflict vivid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-oslo.serialization in Ubuntu. https://bugs.launchpad.net/bugs/1420953 Title: package python-oslo-serialization (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/python2.7/dist- packages/oslo/serialization/__init__.py', which is also in package python-oslo.serialization 1.1.0-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-oslo.serialization/+bug/1420953/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1418590] Re: No ERROR state if image deleted, _base is lost and instance is rescued
My current idea is to stop using cached images at all for the rescue and check if image exists before doing anything bad with instance. In my current implementation attempt to rescue instance with deleted image will not stop instance and log error: Image cad7e9e6-930c-4622-bbd4-b3af79f66914 found but deleted, unable to use it for rescue instance 8f021338-233e-4f4e-937a-596358e487c4. ** Changed in: nova Assignee: (unassigned) => George Shuklin (george-shuklin) ** Changed in: nova Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1418590 Title: No ERROR state if image deleted, _base is lost and instance is rescued To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1418590/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1418590] Re: No ERROR state if image deleted, _base is lost and instance is rescued
** Description changed: State to reproduce: 1. Boot instance from image 2. Delete image 3. Stop nova-compute 4. Remove /var/lib/nova/instances/_base/* 5. start nova-compute 6. Try to rescue instance (nova rescue image) Nova-compute will fail with few traces (see below) and instance get strange state: nova show 290ab4b7-7225-4b74-853a-d342974a2080 +--+--+ | Property | Value | +--+--+ | OS-DCF:diskConfig| AUTO | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-SRV-ATTR:host | pp3 | | OS-EXT-SRV-ATTR:hypervisor_hostname | pp3 | | OS-EXT-SRV-ATTR:instance_name| instance-00f6 | | OS-EXT-STS:power_state | 1 | | OS-EXT-STS:task_state| - | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2015-02-05T14:15:30.00 | | OS-SRV-USG:terminated_at | - | (skip) After that it is impossible to unrescue instance (Cannot 'unrescue' while instance is in vm_state active) or hard-reset (nothing happens). Only nova reset-state helps. - Expected behavior: set it to ERROR state. + Expected behavior: set it to ERROR state or, better, to reject rescue if + no image found. Traces: 2015-02-05 15:59:41.973 7281 INFO nova.virt.libvirt.driver [req-af7026f3-4d85-4899-8452-2b69a3e66123 None] [instance: 290ab4b7-7225-4b74-853a-d342974a2080] Instance failed to shutdown in 60 seconds. 2015-02-05 15:59:42.363 7281 DEBUG nova.virt.driver [-] Emitting event Stopped> emit_event /usr/lib/python2.7/dist-packages/nova/virt/driver.py:1298 2015-02-05 15:59:42.364 7281 INFO nova.compute.manager [-] [instance: 290ab4b7-7225-4b74-853a-d342974a2080] VM Stopped (Lifecycle Event) 2015-02-05 15:59:42.366 7281 INFO nova.virt.libvirt.driver [-] [instance: 290ab4b7-7225-4b74-853a-d342974a2080] Instance destroyed successfully. 2015-02-05 15:59:42.368 7281 INFO nova.virt.libvirt.driver [req-af7026f3-4d85-4899-8452-2b69a3e66123 None] [instance: 290ab4b7-7225-4b74-853a-d342974a2080] Creating image 2015-02-05 15:59:42.369 7281 DEBUG nova.openstack.common.processutils [req-af7026f3-4d85-4899-8452-2b69a3e66123 None] Running cmd (subprocess): sudo nova-rootwrap /etc/nova/rootwrap.conf chown 106 /var/lib/nova/instances/290ab4b7-7225-4b74-853a-d342974a2080/console.log execute /usr/lib/python2.7/dist-packages/nova/openstack/common/processutils.py:161 2015-02-05 15:59:42.389 7281 DEBUG nova.compute.manager [-] [instance: 290ab4b7-7225-4b74-853a-d342974a2080] Synchronizing instance power state after lifecycle event "Stopped"; current vm_state: active, current task_state: rescuing, current DB power_state: 1, VM power_state: 4 handle_lifecycle_event /usr/lib/python2.7/dist-packages/nova/compute/manager.py: 2015-02-05 15:59:42.405 7281 DEBUG nova.openstack.common.processutils [req-af7026f3-4d85-4899-8452-2b69a3e66123 None] Result was 0 execute /usr/lib/python2.7/dist-packages/nova/openstack/common/processutils.py:195 2015-02-05 15:59:42.406 7281 DEBUG nova.openstack.common.lockutils [req-af7026f3-4d85-4899-8452-2b69a3e66123 ] Created new semaphore "70a880bdefde82d942a92de4c180c202e6090dd6" internal_lock /usr/lib/python2.7/dist-packages/nova/openstack/common/lockutils.py:206 2015-02-05 15:59:42.406 7281 DEBUG nova.openstack.common.lockutils [req-af7026f3-4d85-4899-8452-2b69a3e66123 ] Acquired semaphore "70a880bdefde82d942a92de4c180c202e6090dd6" lock /usr/lib/python2.7/dist-packages/nova/openstack/common/lockutils.py:229 2015-02-05 15:59:42.406 7281 DEBUG nova.openstack.common.lockutils [req-af7026f3-4d85-4899-8452-2b69a3e66123 ] Attempting to grab external lock "70a880bdefde82d942a92de4c180c202e6090dd6" external_lock /usr/lib/python2.7/dist-packages/nova/openstack/common/lockutils.py:178 2015-02-05 15:59:42.406 7281 DEBUG nova.openstack.common.lockutils [req-af7026f3-4d85-4899-8452-2b69a3e66123 ] Got file lock "/var/lib/nova/instances/locks/nova-70a880bdefde82d942a92de4c180c202e6090dd6" acquire /usr/lib/python2.7/dist-packages/nova/openstack/common/lockutils.py:93 2015-02-05 15:59:42.407 7281 DEBUG nova.openstack.common.lockutils [req-af7026f3
[Bug 1401188] [NEW] glance-client fails if too many images: 'maximum recursion depth exceeded in cmp'
Public bug reported: If tenant got too much images, glance client failed with message 'maximum recursion depth exceeded in cmp'. time glance image-list |wc -l maximum recursion depth exceeded in cmp 0 real9m23.401s user0m2.607s sys 0m0.207s select count(*) from images ; +--+ | count(*) | +--+ |32864 | +--+ python-glanceclient for juno (ubuntu-cloud-archive). ii python-glanceclient 1:0.14.0-0ubuntu1 ** Affects: python-glanceclient Importance: Undecided Status: New ** Affects: python-glanceclient (Ubuntu) Importance: Undecided Status: New ** Also affects: python-glanceclient (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-glanceclient in Ubuntu. https://bugs.launchpad.net/bugs/1401188 Title: glance-client fails if too many images: 'maximum recursion depth exceeded in cmp' To manage notifications about this bug go to: https://bugs.launchpad.net/python-glanceclient/+bug/1401188/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1401154] Re: Error: "global name '_' is not defined" during glance image-create
** Also affects: python-glanceclient (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-glanceclient in Ubuntu. https://bugs.launchpad.net/bugs/1401154 Title: Error: "global name '_' is not defined" during glance image-create To manage notifications about this bug go to: https://bugs.launchpad.net/python-glanceclient/+bug/1401154/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1358147] Re: ProgrammingError: You have an error in your SQL syntax 'INSERT INTO meteringlabels'
What kind of data do you need? That installation is still running, I can gather it. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1358147 Title: ProgrammingError: You have an error in your SQL syntax 'INSERT INTO meteringlabels' To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1358147/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1358147] [NEW] ProgrammingError: You have an error in your SQL syntax 'INSERT INTO meteringlabels'
Public bug reported:
Installation works about few months, got this message in logstash.
Happens once, there is no surrounding activity (no requests to API).
Havanna, ubuntu-cloud-archive, 2013.2.3-0ubuntu1.1
Aug 17 21:48:59 api1 neutron.openstack.common.db.sqlalchemy.session[12400]:
ERROR DB exception wrapped.
Traceback (most recent call last):
File
"/usr/lib/python2.7/dist-packages/neutron/openstack/common/db/sqlalchemy/session.py",
line 524, in _wrap
return f(*args, **kwargs)
File
"/usr/lib/python2.7/dist-packages/neutron/openstack/common/db/sqlalchemy/session.py",
line 718, in flush
return super(Session, self).flush(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 1818,
in flush
self._flush(objects)
File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 1936,
in _flush
transaction.rollback(_capture_exception=True)
File "/usr/lib/python2.7/dist-packages/sqlalchemy/util/langhelpers.py", line
58, in __exit__
compat.reraise(exc_type, exc_value, exc_tb)
File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 1900,
in _flush
flush_context.execute()
File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/unitofwork.py", line
372, in execute
rec.execute(self)
File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/unitofwork.py", line
525, in execute
uow
File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/persistence.py", line
64, in save_obj
table, insert)
File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/persistence.py", line
541, in _emit_insert_statements
execute(statement, multiparams)
File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 662,
in execute
params)
File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 761,
in _execute_clauseelement
compiled_sql, distilled_params
File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 874,
in _execute_context
context)
File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1024,
in _handle_dbapi_exception
exc_info
File "/usr/lib/python2.7/dist-packages/sqlalchemy/util/compat.py", line 195,
in raise_from_cause
reraise(type(exception), exception, tb=exc_tb)
File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 867,
in _execute_context
context)
File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/default.py", line
324, in do_execute
cursor.execute(statement, parameters)
File "/usr/lib/python2.7/dist-packages/MySQLdb/cursors.py", line 174, in
execute
self.errorhandler(self, exc, value)
File "/usr/lib/python2.7/dist-packages/MySQLdb/connections.py", line 36, in
defaulterrorhandler
raise errorclass, errorvalue
ProgrammingError: (ProgrammingError) (1064, 'You have an error in your
SQL syntax; check the manual that corresponds to your MySQL server
version for the right syntax to use near \':
"\'eaa6e8e248ce4f3784282b0c3f51384a\'", u\'created_at\':
"\'2014-08-05T06:34:28+00:\' at line 1') 'INSERT INTO meteringlabels
(tenant_id, id, name, description) VALUES (%s, %s, %s, %s)'
({u'keystone_tenant_id': u'eaa6e8e248ce4f3784282b0c3f51384a',
u'created_at': u'2014-08-05T06:34:28+00:00', u'updated_at':
u'2014-08-05T06:34:28+00:00', u'admin_blocked': False, u'id': 817,
u'blocked': False}, '81070432-d514-4606-b564-e7f76138d985', 'billable',
'')
** Affects: cloud-archive
Importance: Undecided
Status: New
** Affects: neutron
Importance: Undecided
Status: New
** Affects: neutron (Ubuntu)
Importance: Undecided
Status: New
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Installation works about few months, got this message in logstash.
Happens once, there is no surrounding activity (no requests to API).
+ Havanna, ubuntu-cloud-archive, 2013.2.3-0ubuntu1.1
+
Aug 17 21:48:59 api1 neutron.openstack.common.db.sqlalchemy.session[12400]:
ERROR DB exception wrapped.
Traceback (most recent call last):
- File
"/usr/lib/python2.7/dist-packages/neutron/openstack/common/db/sqlalchemy/session.py",
line 524, in _wrap
- return f(*args, **kwargs)
- File
"/usr/lib/python2.7/dist-packages/neutron/openstack/common/db/sqlalchemy/session.py",
line 718, in flush
- return super(Session, self).flush(*args, **kwargs)
- File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line
1818, in flush
- self._flush(objects)
- File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line
1936, in _flush
- transaction.rollback(_capture_exception=True)
- File "/usr/lib/python2.7/dist-packages/sqlalchemy/util/langhelpers.py",
line 58, in __exit__
- compat.reraise(exc_type, exc_value, exc_tb)
- File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line
1900,
[Bug 1286209] Re: unhandled trace if no namespaces in metering agent
I was able to fix this by ignoring exception in __exit__() function. But still, proper solution should filter out routers from other network nodes. ** Changed in: neutron Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1286209 Title: unhandled trace if no namespaces in metering agent To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1286209/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1286209] Re: unhandled trace if no namespaces in metering agent
I still see than bug and definitively can reproduce it. If router is placed on other network node, metering agent fail, because it expecting to see network namespace for that router on own network node. There is no filtering 'our' router or 'not our'. It will works on single-node installation, but fails on multi-node. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1286209 Title: unhandled trace if no namespaces in metering agent To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1286209/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1324856] Re: Ubuntu source package for neutron can not be rebuild
Yes, rebuilding from clean sources is working. But still, this is 'broken source package' according to debian guys. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1324856 Title: Ubuntu source package for neutron can not be rebuild To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1324856/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1324856] [NEW] Ubuntu source package for neutron can not be rebuild
Public bug reported: Ubuntu's source package for neutron can not be rebuild twice: 1. There is no proper clean target. 2. neutron.egg-info changes after build That cause problem when package is build twice from same source. 1st build is fine, 2nd cause following errors: (each type of error cited once) 1. dpkg-source: warning: newly created empty file 'build/lib.linux-x86_64-2.7/neutron/openstack/common/__init__.py' will not be represented in diff 2. dpkg-source: error: cannot represent change to neutron/__init__.pyc: binary file contents changed 3. dpkg-source: info: local changes detected, the modified files are: neutron-2013.2.3/neutron.egg-info/entry_points.txt neutron-2013.2.3/neutron.egg-info/requires.txt ** Affects: neutron (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1324856 Title: Ubuntu source package for neutron can not be rebuild To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1324856/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1286209] Re: unhandled trace if no namespaces in metering agent
Can you check if you got no namespaces on machine during that time (ip netns list)? I think that bug happens when l3/dhcp agents remove it own namespaces from machine. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1286209 Title: unhandled trace if no namespaces in metering agent To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1286209/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1286209] Re: unhandled trace if no namespaces in metering agent
Hello. 1. I was slightly wrong, not 'agent', but router (and same thing for dhcp-agent). The means if l3-agent got no routers on itself, trace happens. neutron l3-agent-router-remove allow to remove routers from host. 2. Nope, I think this is default behavior for metering agent, because there is no namespaces at all (before l3-agent creates them for router). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1286209 Title: unhandled trace if no namespaces in metering agent To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1286209/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1287050] [NEW] No auth_uri in api-paste.conf (Configure a Block Storage Service controller in OpenStack Installation Guide for Ubuntu 12.04 (LTS) - havana)
Public bug reported: Page says nothing about auth_uri. Without it cinder-api.log complains: WARNING keystoneclient.middleware.auth_token [-] Configuring auth_uri to point to the public identity endpoint is required; clients may not be able to authenticate against an admin endpoint Proposal: Add auth_uri=http://controller:5000/ to api-paste.ini (near auth_host). --- Built: 2014-03-02T10:12:18 00:00 git SHA: 4c667a6daf2c5a25efdf7e59ec4b76960879ed76 URL: http://docs.openstack.org/havana/install-guide/install/apt/content/cinder-controller.html source File: file:/home/jenkins/workspace/openstack-install-deploy-guide-ubuntu/doc/install-guide/section_cinder-controller.xml xml:id: cinder-controller ** Affects: cinder (Ubuntu) Importance: Undecided Status: New ** Project changed: openstack-manuals => cinder (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cinder in Ubuntu. https://bugs.launchpad.net/bugs/1287050 Title: No auth_uri in api-paste.conf (Configure a Block Storage Service controller in OpenStack Installation Guide for Ubuntu 12.04 (LTS) - havana) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1287050/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1286209] Re: unhandled trace if no namespaces in metering agent
any agent solve the problem (inc. dhcp-agent). Host without agents cause traces. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1286209 Title: unhandled trace if no namespaces in metering agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1286209/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1286209] Re: unhandled trace if no namespaces in metering agent
neutron-plugin-metering-agent1:2013.2.1-0ubuntu1~cloud0 ** Project changed: neutron => neutron (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1286209 Title: unhandled trace if no namespaces in metering agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1286209/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1249708] Re: Missing neutron-ovs-cleanup service
It should start on every compute and network node. It clear up all strange artefacts saved by ovs-vsctl. How to get 'strange artifacts': On any working compute/network node with active networking on instances perform any operations on ovs-vsctl, f.e.: ovs-vsctl add-br just_empty_bridge ovs-vsctl del-br just_empty_bridge ovs will save all current tap/tun qr-* interfaces in br-int/br-ext bridges and restore them on next boot inside own config, even if they are not available at server start. This will cause problems for existing instances during their startup. neutron-ovs-cleanup should run during startup on all non-diskless nodes to ensure nothing strange is exists in bridges prior fists instance/agent start. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1249708 Title: Missing neutron-ovs-cleanup service To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1249708/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
