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
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 (us
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 mana
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
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 Ubunt
@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
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
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 m
** 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 r
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 no
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
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)
ProcVersionSigna
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 mem
** 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 inst
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 ;
+--
** 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 na
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
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
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
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, b
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:
Ub
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 cite
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.
h
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
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
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 me
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
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
28 matches
Mail list logo
