** Changed in: cinder (Ubuntu Raring)
Status: Fix Committed = Fix Released
--
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/1126378
Title:
SchedulerHostFilterNotFound:
** Changed in: cinder (Ubuntu)
Status: Fix Committed = Fix Released
--
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/1097869
Title:
testsuite is failing on ubuntu
To manage
While in my experience, bugs in Ubuntu get ignored anyway, maybe the
little patch icon will help?
** Attachment added: 6ceeb6421231.txt
https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1138905/+attachment/3630446/+files/6ceeb6421231.txt
--
You received this bug notification because
I was experiencing a similar problem as described by submitter.
The name resolution of the short name failed, subsequently the name
resolution of the fqdn also failed. After 10-15 seconds, the fqdn
resolved again, only to fail again after trying the short name.
The solution described by Thomas
** Changed in: tomcat7 (Ubuntu Raring)
Milestone: ubuntu-13.04-beta-1 = ubuntu-13.04
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat7 in Ubuntu.
https://bugs.launchpad.net/bugs/1163803
Title:
tomcat7 ftbfs in raring
To
Hello,
finally i didn't deactivate the weekly crond tasks, I configured the weekly
crond tasks to be run at 05:47 AM every sunday.
Anyway, last sunday the apache2 process died again. This time at
05:15:13 AM.
Any update in this bug report?
Thanks in advanced!
Regards,
--
You received this
Howdy,
I know that in my case, this was definitely an MTU problem, and it
exhibits exactly the behavior stated above.
to test this, call
ping -M do -s 1500 host
If it goes through, this is probably not your issue. If it does not, try
lowering the -s value until it does go through. If the
Sorry, I don't think this bug report can make any progress until we've
confirmed that the problem affects others (so we know it's not a
hardware fault or local configuration issue) and we have steps a
developer can use to reproduce the problem on his system.
--
You received this bug notification
Resubmitted changelogs for that SRU
** Description changed:
This is a meta-bug used for tracking progress of new updates to Nova,
Horizon, Keystone.
- nova (2012.1.4+stable-20121217-9f277e38-0ubuntu1) precise-proposed;
+ nova (2012.1.4+stable-20130402-e52e6912-0ubuntu1) precise-proposed;
The attachment 6ceeb6421231.txt seems to be a patch. If it isn't,
please remove the patch flag from the attachment, remove the patch
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray,
Thank you for reporting this bug and helping to make Ubuntu better.
Confirmed in Raring, vim-puppet 2.7.18-1ubuntu2. Looks like this was
fixed in Debian 2.7.18-2.
** Changed in: puppet (Ubuntu)
Status: New = Triaged
** Changed in: puppet (Ubuntu)
Importance: Undecided = Medium
** Bug
Public bug reported:
tomcat7 FTBFS due to the fact that the certificates and keystores used
during testing expired at the end of feb 2013. This is fixed in more
recent upstream releases.
** Affects: tomcat7 (Ubuntu)
Importance: High
Status: Triaged
** Affects: tomcat7 (Ubuntu
I've added a simple reproduce for bug 1124384 under lxc . It seems
likely to me at least that this bug and that one are related.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
** Changed in: puppet (Debian)
Status: Unknown = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1163927
Title:
indent/puppet.vim required by vim-addons-manager
** Description changed:
Guys,
- During my new tests, I tried to create two nodes simultaneously (both
+ During my new tests, I tried to create two nodes simultaneously (both
via DHCP + PXE, not by clicking +Add node) and I hit this problem:
- Same MAC Address, two different IPs:
+
** Branch linked: lp:ubuntu/raring-proposed/tomcat7
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat7 in Ubuntu.
https://bugs.launchpad.net/bugs/1166187
Title:
tomcat7 FTBFS due to expired test certificates
To manage
This bug was fixed in the package tomcat7 - 7.0.35-1~exp2ubuntu1
---
tomcat7 (7.0.35-1~exp2ubuntu1) raring; urgency=low
* Fix FTBFS due to expired test certificates (LP: #1166187):
- d/keystores/*.jks: Newer keystores from upstream 7.0.39.
- d/rules: Install newer keystores
Fixed by merge, attached.
** Patch added: ubuntu.debdiff
https://bugs.launchpad.net/debian/+source/puppet/+bug/1163927/+attachment/3631138/+files/ubuntu.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
** Patch added: debian.debdiff
https://bugs.launchpad.net/debian/+source/puppet/+bug/1163927/+attachment/3631139/+files/debian.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
** Attachment added: puppet_2.7.18-4ubuntu1_amd64.build
https://bugs.launchpad.net/debian/+source/puppet/+bug/1163927/+attachment/3631140/+files/puppet_2.7.18-4ubuntu1_amd64.build
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Patch added: isc-dhcp_4.1.ESV-R4-0ubuntu5.6.1.precise.debdiff
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1069570/+attachment/3631196/+files/isc-dhcp_4.1.ESV-R4-0ubuntu5.6.1.precise.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Description changed:
- Guys,
-
- During my new tests, I tried to create two nodes simultaneously (both
- via DHCP + PXE, not by clicking +Add node) and I hit this problem:
+ [Impact]
+ During my new tests, I tried to create two nodes simultaneously (both via
DHCP + PXE, not by clicking
Looks like upstream has a pending release to fix this issue positive
testing results from community.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1068145
Title:
Fix for
** Changed in: walinuxagent (Ubuntu Precise)
Importance: Medium = Critical
** Changed in: walinuxagent (Ubuntu Quantal)
Importance: Medium = Critical
** Description changed:
+ Upgrade walinuxagent to 1.3.2 to enhance logging for Azure platform
+ issues.
+
SRU justification
Impact
Yes, we're planning to release the fix for this issue in Puppet 3.2
which will hopefully go out as RC1 at the end of this week.
I'm not sure how difficult the backport to 2.7 will be, but we did so a
slight refactor after fixing the issue, so it is non-trivial at this
point. If you have any
Thank you for reporting this bug and helping to make Ubuntu better.
Could you please check to see if this problem exists in the latest
upstream release, and/or the latest Ubuntu development release?
** Changed in: tomcat7 (Ubuntu)
Importance: Undecided = Medium
--
You received this bug
Public bug reported:
LXC 0.9.0 has been released on Saturday. As mentioned in bug 1157227, I
think it'd be a good thing to release 13.04 with the final stable
version of LXC instead of the release candidate.
LXC was technically feature frozen between rc1 and final, however we had
to do a couple
Looks good to me, go nuts.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1166286
Title:
[FFe] LXC 0.9 final
To manage notifications about this bug go to:
** Summary changed:
- lxc-ls crashed with SIGABRT in Py_FatalError()
+ lxc scripts break when user has PYTHONPATH
** Summary changed:
- lxc scripts break when user has PYTHONPATH
+ lxc scripts break when user has PYTHONPATH set
** Description changed:
- Occurred when deploying the juju mysql
** Changed in: apache2 (Ubuntu)
Importance: Undecided = Wishlist
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1164981
Title:
Web sockets (wss) not supported
To manage
I'm unconvinced this is a problem with the use of lxc in juju as opposed
to a general issue with the lxc scripts.
** Changed in: juju
Status: New = Incomplete
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are
@arnose
was this image a simple installation of quantal? Can you reproduce this
by creating images int he same way?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1047040
Title:
What exactly would the lxc scripts be doing wrong? Since the work around
involves the extraordinary option of dropping the environment, I think
what ever is forcing a py2 path is being naughty.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
On 08/04/13 18:54, Curtis Hovey wrote:
What exactly would the lxc scripts be doing wrong? Since the work around
involves the extraordinary option of dropping the environment, I think
what ever is forcing a py2 path is being naughty.
I'd agree here. A python2 app calling a python3 app should
** Patch removed: isc-dhcp_4.1.ESV-R4-0ubuntu5.6.1.precise.debdiff
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1069570/+attachment/3631196/+files/isc-dhcp_4.1.ESV-R4-0ubuntu5.6.1.precise.debdiff
** Patch removed: isc-dhcp_4.2.4-1ubuntu10.1.quantal.debdiff
** Patch added: isc-dhcp_4.2.4-1ubuntu10.3.quantal.debdiff
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1069570/+attachment/3631785/+files/isc-dhcp_4.2.4-1ubuntu10.3.quantal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Public bug reported:
This will pick up a few bugfixes from Debian that I think are worth
having in Raring.
** Affects: exim4 (Ubuntu)
Importance: Medium
Status: Triaged
** Tags: raring upgrade-software-version
--
You received this bug notification because you are a member of
** Patch added: debian.debdiff
https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1166383/+attachment/3631875/+files/debian.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to exim4 in Ubuntu.
** Patch added: ubuntu.debdiff
https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1166383/+attachment/3631876/+files/ubuntu.debdiff
** Changed in: exim4 (Ubuntu)
Status: New = Triaged
** Changed in: exim4 (Ubuntu)
Importance: Undecided = Medium
** Tags added: raring
** Attachment added: exim4_4.80-7ubuntu1_amd64.build
https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1166383/+attachment/3631904/+files/exim4_4.80-7ubuntu1_amd64.build
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to exim4 in
It is TM1 that I see in the logs.
Thanks for the detail explanation. The only thing it doesn't explain, is
why this only happens when using Ubuntu and not Windows... I'll be fore
to revert if it continues to crash.
Ubuntu will allow systems temp to go up without stop? Shouldn't it slow
down
To make thinking this is an LXC bug as oppose to a JuJu one because lxc-
ls is python and so can be affected by environment variables makes as
much sense as blaming a C program for having a different behaviour when
your code change PATH or LD_PRELOAD.
Marking this invalid for LXC (I'm not opposed
** Package changed: lm-sensors (Ubuntu) = ubuntu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
https://bugs.launchpad.net/bugs/1163573
Title:
Ubuntu 12.10 overheats my laptop until it shutdowns without notice
Public bug reported:
After I created a thousand new flavors (to enable some automation), with
IDs 1000-1999, nova flavor-list now displays flavor 1, followed by
1000-1998, and then stops.
Flavors 1999 and 2-6 are still valid and usable, just absent from the
output of flavor-list (flavor-show is
** Tags added: prodstack
--
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/1166455
Title:
nova flavor-list only shows 1000 flavors
To manage notifications about this bug go 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
This bug was fixed in the package lxc - 0.9.0-0ubuntu1
---
lxc (0.9.0-0ubuntu1) raring; urgency=low
* New upstream release (0.9.0) (LP: #1166286)
- New features
(fixing a regression for 0.8/0.9alpha who relied on --keep-env)
+ lxc-attach: Add --clear-env and
47 matches
Mail list logo
