I have determined this is caused by SQL backends. a SQL backend on
ceilometer apparently is a very bad idea. This should be made into a
documentation bug.
** No longer affects: ceilometer (Ubuntu)
** Summary changed:
- 'ceilometer *-list' too slow to respond
+ Using SQL backend is
From what I am gathering.. at request time there is a large join.. which
doesn't take that much time.. Then there are thousands of small select
statements recursively looping through the joined data. This is highly
ineffective and there is probability that the issue is exponential.
** Also
** Summary changed:
- 'ceilometer meter-list' too slow to respond
+ 'ceilometer *-list' too slow to respond
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1180438
Title:
'ceilometer *-list' too
If this wont be fixed in Grizzly, then the offending python-
quantumclient commit should be pulled from grizzly repos. It cannot be
left in place without package remaining broken.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
If this wont be fixed in Grizzly, then the offending python-
quantumclient commit should be pulled from grizzly repos. It cannot be
left in place without package remaining broken.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the workaround Linus. Will give it a shot... Do we expect
this package to make it into ubuntu soon? Or are there conflicts with
other packages and we will have to wait a while?
Thanks Again.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Thanks for the workaround Linus. Will give it a shot... Do we expect
this package to make it into ubuntu soon? Or are there conflicts with
other packages and we will have to wait a while?
Thanks Again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Latest python-ceilometerclient requires python-cliff 1.3.2 which is
unavailable in the test ppa or any other ubuntu repos. This makes the
existing version of Quantum in http://ppa.launchpad.net/openstack-
ubuntu-testing/grizzly-trunk-testing/ubuntu broken:
# dpkg --list
Ticket which introduced issue: https://bugs.launchpad.net/python-
quantumclient/+bug/1165962
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-quantumclient in Ubuntu.
https://bugs.launchpad.net/bugs/1170849
Title:
Cliff 1.3.2
Ticket which introduced issue: https://bugs.launchpad.net/python-
quantumclient/+bug/1165962
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1170849
Title:
Cliff 1.3.2 is not available
To manage
Public bug reported:
Latest python-ceilometerclient requires python-cliff 1.3.2 which is
unavailable in the test ppa or any other ubuntu repos. This makes the
existing version of Quantum in http://ppa.launchpad.net/openstack-
ubuntu-testing/grizzly-trunk-testing/ubuntu broken:
# dpkg --list
** Also affects: python-quantumclient (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-quantumclient in Ubuntu.
https://bugs.launchpad.net/bugs/1165962
Title:
unit test
** Also affects: python-quantumclient (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1165962
Title:
unit test fails with the latest commit
To
I no longer have this issue as of 04/08 build
2:2.2.1.11.ge901c5f+git201304081157~precise-0ubuntu1 .
** Changed in: python-quantumclient (Ubuntu)
Status: Confirmed = In Progress
** No longer affects: python-quantumclient (Ubuntu)
--
You received this bug notification because you are a
I no longer have this issue as of 04/08 build
2:2.2.1.11.ge901c5f+git201304081157~precise-0ubuntu1 .
** Changed in: python-quantumclient (Ubuntu)
Status: Confirmed = In Progress
** No longer affects: python-quantumclient (Ubuntu)
--
You received this bug notification because you are a
** Changed in: quantum
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-quantumclient in Ubuntu.
https://bugs.launchpad.net/bugs/1165059
Title:
Grizzly testing packages : python-quantumclient
** Changed in: quantum
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1165059
Title:
Grizzly testing packages : python-quantumclient installation/upgrade
fails
To
** Also affects: python-quantumclient (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-quantumclient in Ubuntu.
https://bugs.launchpad.net/bugs/1165059
Title:
Grizzly
Note that python-ceilometer had same issue recently:
https://bugs.launchpad.net/ceilometer/+bug/1102110. Perhaps fix for that
will help here..
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-quantumclient in Ubuntu.
What is the status on this? As of today the repository is still broken.
Getting:
Preparing to replace python-quantumclient 1:2.2.0-0ubuntu1~cloud0 (using
.../python-quantumclient_2%3a2.2.1.7.g22fd452+git201304040531~precise-0ubuntu1_all.deb)
...
Unpacking replacement python-quantumclient ...
** Branch linked: lp:~openstack-ubuntu-testing/ceilometer/grizzly
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1102110
Title:
Grizzly testing packages : python-ceilometer installation fails
To
I realized that this is actually a completely different package then the
original ticket. However both have python boto as conflict. I am going
to open another ticket for the quantum specific issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: python-quantumclient (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1165059
Title:
Grizzly testing packages :
Note that python-ceilometer had same issue recently:
https://bugs.launchpad.net/ceilometer/+bug/1102110. Perhaps fix for that
will help here..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1165059
** Also affects: ubuntu
Importance: Undecided
Status: New
** No longer affects: ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1008587
Title:
SQL token backend does not remove
I have now also tried:
--volume_scheduler_driver=nova.scheduler.simple.SimpleScheduler
And have exact same bad behavior when it hits the second sever. Could
this be LUN number conflicts? They both default to LUN0.
** Description changed:
OS: Ubuntu 12.04
Arch: amd64
- Nova Version:
Ok after tracing the Nexenta logs I have found that the second Nexenta
server is never contacted when the failure occurs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1039763
Title:
Multiple
Aha Ok it requires that the nova-volume services run on separate
hosts! I realized this after looking at service table in db and seeing
only one nova-volume entry. Having them on different hosts is not an
option for us. I am going to write patch that allows override of
hostname to in essence
What is the timeframe for getting this released to main ubuntu repo? or
at least in a stable ppa?
--
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/1014925
Title:
API
That's great news Adam! We very much look forward to its deb release.
--
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/1014925
Title:
API 'v1.1/{tenant_id}/os-hosts' does not return a
What is the timeframe for getting this released to main ubuntu repo? or
at least in a stable ppa?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1014925
Title:
API 'v1.1/{tenant_id}/os-hosts' does
That's great news Adam! We very much look forward to its deb release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1014925
Title:
API 'v1.1/{tenant_id}/os-hosts' does not return a list of hosts
Note that both nova-volume servies are on same server.. From what I can
tell it is doing round robin between the two services when I create
volumes. I do notice that the service table in db only references one
service.. Is this to be expected?
** Also affects: ubuntu
Importance: Undecided
Note that if I switch the order in which they start, the second one to
start is always one to fail creation. Both work ok on their own.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1039763
Title:
Ha! Ok I see how you guys do this now. Thanks for bearing with me as I
learn the ropes. And thank you for your support getting this patch
pushed to precise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have installed the proposed python and it tested successfully. No bad
characters seen in logs.
** Changed in: python2.7 (Ubuntu Precise)
Status: Fix Committed = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have set precise to Confirmed. I do not have a Quantal system to
confirm the Quantal change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1029640
Title:
Bad characters in Python logger output
Any python app using the std python logger to syslog will exhibit the
behavior. Openstack is one example. it is apparent when tailing the
syslog. I am willing to write up a test case however I have no idea what
format you guys use.. can you point me to previous ones?
--
You received this bug
Yeah I can do that.. WIll write up a code snippet and attach with
details.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1029640
Title:
Bad characters in Python logger output when using rsyslog
To
ok this code will reproduce. Note that key was to convert to utf8 before
sending to syslog.
# vim: tabstop=4 shiftwidth=4 softtabstop=4
import logging
from logging.handlers import SysLogHandler
# our new audit level
# NOTE(jkoelker) Since we synthesized an audit level, make the logging
#
btw output from above code:
# /usr/bin/python log_stuff.py
Jul 27 13:52:04 mc root: #277root: AUDIT: TEST LOGER FROM PYTHON
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1029640
Title:
Bad
You sure? This commit diff accurately applies the fix (removal of the
BOM addition): http://hg.python.org/cpython/rev/af46a001d5ec
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1029640
Title:
Bad
Public bug reported:
Ubuntu 12.0.4 LTS 64bit
python2.7-minimal 2.7.3-0ubuntu3
rsyslog5.8.6-1ubuntu8
Python converts all syslog messages to UTF8 before sending to syslog. It
also prepends the Byte Order Mark (BOM) of the Unicode Standard. This
** Description changed:
Ubuntu 12.0.4 LTS 64bit
- python2.7-minimal 2.7.3-0ubuntu3
+ python2.7-minimal 2.7.3-0ubuntu3
rsyslog5.8.6-1ubuntu8
Python converts all syslog messages to UTF8 before sending to syslog. It
also
Filed bug with Rsyslog also:
http://bugzilla.adiscon.com/show_bug.cgi?id=346
** Bug watch added: bugzilla.adiscon.com/ #346
http://bugzilla.adiscon.com/show_bug.cgi?id=346
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
All Related Tickets:
https://bugs.launchpad.net/openstack-common/+bug/1029116
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1029640
http://bugzilla.adiscon.com/show_bug.cgi?id=346
http://bugs.python.org/issue15462
** Bug watch added: Python Roundup #15462
This indeed is a known Python bug (http://bugs.python.org/msg158447).
Ubuntu Python is out of date.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1029640
Title:
Bad characters in Python logger
Public bug reported:
API 'v1.1/{tenant_id}/os-hosts' does not return a list of hosts.
Instead it returns an empty set.
This is a known bug and was fixed for Folsom. However it has not been fixed for
Essex. Last good version was 2012.1-0ubuntu2.3. Link to nova bug:
Public bug reported:
API 'v1.1/{tenant_id}/os-hosts' does not return a list of hosts.
Instead it returns an empty set.
This is a known bug and was fixed for Folsom. However it has not been fixed for
Essex. Last good version was 2012.1-0ubuntu2.3. Link to nova bug:
I am effected by this also after updating packages
apparmor apport cpp-4.6 dkms fuse gcc-4.6 gcc-4.6-base
language-selector-common libapparmor1 libbsd0 libfuse2 libgc1c2 libgcc1
libgomp1 libiw30 libpulse0 libquadmath0 libstdc++6
libvirt-bin libvirt0 libx11-6 libx11-data libxext6
Note my post above is for amd64. Attempting Beta1 fresh install now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933351
Title:
Crashes on startup with segfault
To manage notifications about this
Hi Here is Log from CLC that corresponds to CC log you have seen above
(see attached). An interesting note about the attached log. There is
only one successful vm in the secgroup. All other fail with the attached
and above errors. When I create another secgroup, the new one behaves
normally and I
Forgot the log.
** Attachment added: clc-debug.log
https://bugs.launchpad.net/ubuntu/lucid/+source/eucalyptus/+bug/564355/+attachment/1715609/+files/clc-debug.log
--
Second euca-run-instance request in same security group causes eucalyptus to
remove network assoicated with security group
Hi Here is Log from CLC that corresponds to CC log you have seen above
(see attached). An interesting note about the attached log. There is
only one successful vm in the secgroup. All other fail with the attached
and above errors. When I create another secgroup, the new one behaves
normally and I
Forgot the log.
** Attachment added: clc-debug.log
https://bugs.launchpad.net/ubuntu/lucid/+source/eucalyptus/+bug/564355/+attachment/1715609/+files/clc-debug.log
--
Second euca-run-instance request in same security group causes eucalyptus to
remove network assoicated with security group
This also Effects 1.6.2 CentOS release. When ADDRPERNET is set to 256 it
causes same behavior with this error:
[Wed Aug 11 08:22:12 2010][005109][EUCADEBUG ] RunInstances(): params:
userId=admin, emiId=emi-54A01BEF, kernelId=eki-5A861EB7, ramdiskId=UNSET,
Actually this shows itself when at 64 or 128 also.
** Also affects: eucalyptus (CentOS)
Importance: Undecided
Status: New
--
Second euca-run-instance request in same security group causes eucalyptus to
remove network assoicated with security group
This also Effects 1.6.2 CentOS release. When ADDRPERNET is set to 256 it
causes same behavior with this error:
[Wed Aug 11 08:22:12 2010][005109][EUCADEBUG ] RunInstances(): params:
userId=admin, emiId=emi-54A01BEF, kernelId=eki-5A861EB7, ramdiskId=UNSET,
Actually this shows itself when at 64 or 128 also.
** Also affects: eucalyptus (CentOS)
Importance: Undecided
Status: New
--
Second euca-run-instance request in same security group causes eucalyptus to
remove network assoicated with security group
59 matches
Mail list logo
