Public bug reported:
When using dhclient to renew IP, /etc/dhcp3/dhclient-enter-hooks.d/samba is
called.
Unfortunatly, this script use an old method to reload smbd
(/usr/sbin/invoke-rc.d smbd reload).
This call give some error messages.
papounet@amd8papou:~$ sudo dhclient
Rather than invoking
** Changed in: glance
Status: Fix Committed = Fix Released
** Changed in: glance
Milestone: None = grizzly-2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-webob in Ubuntu.
https://bugs.launchpad.net/bugs/1083155
** Changed in: keystone
Status: Fix Committed = Fix Released
** Changed in: keystone
Milestone: None = grizzly-2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/1079216
** Changed in: quantum
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to quantum in Ubuntu.
https://bugs.launchpad.net/bugs/1081664
Title:
At times a instance will not receive an IP address
** Changed in: quantum
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to quantum in Ubuntu.
https://bugs.launchpad.net/bugs/1065276
Title:
Quantum test suite leaks memory like a sieve
To
** Changed in: nova
Status: Fix Committed = Fix Released
** Changed in: nova
Milestone: None = grizzly-2
--
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/1080406
Title:
** Changed in: nova
Status: Fix Committed = Fix Released
** Changed in: nova
Milestone: None = grizzly-2
--
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/861504
Title:
Hi,
I have been trying to run a test against the package in quantal-proposed
this morning but it is not clear to me how to get cloud-init to use the
package in proposed. Adding quantal-proposed as a package source is not
working out because it comes too late in the process. The package in
** Changed in: glance
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to glance in Ubuntu.
https://bugs.launchpad.net/bugs/1057322
Title:
Image fails to upload to swift: TypeError: object of
Tested 0.6.3-0ubuntu1.3 on precise and 0.7.0-0ubuntu2.2 on quantal, both
working great.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
Tested 0.6.3-0ubuntu1.3 on precise and 0.7.0-0ubuntu2.2 on quantal, both
working great.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
You have been subscribed to a public bug:
root@cinder:~# apt-get install cinder-common
Reading package lists... Done
Building dependency tree
Reading state information... Done
cinder-common is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully
** Changed in: nova
Status: Fix Committed = Fix Released
** Changed in: nova
Milestone: None = grizzly-2
--
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/1029430
Title:
KVM
Looks like a user-side bug (user probably created the cinder group by
hand). if not, that would be a packaging issue.
** Project changed: cinder = cinder (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cinder in Ubuntu.
** Changed in: nova
Status: Fix Committed = Fix Released
** Changed in: nova
Milestone: None = grizzly-2
--
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/1057279
Title:
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I regret that I cannot understand your report. Please could you clarify?
In particular, please could you post precise steps to reproduce your
bug, exactly what you expect to see, and exactly what is happening
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libcgroup in Ubuntu.
https://bugs.launchpad.net/bugs/1093661
Title:
cgrulesengd fails to start
To manage notifications
Thanks for taking the time to report this bug and helping to make Ubuntu
better. Since the package referred to in this bug is in universe or
multiverse, it is community maintained. If you are able, I suggest
coordinating with upstream and posting a debdiff for this issue. When a
debdiff is
Thanks for taking the time to report this bug and helping to make Ubuntu
better. Since the package referred to in this bug is in universe or
multiverse, it is community maintained. If you are able, I suggest
coordinating with upstream and posting a debdiff for this issue. When a
debdiff is
** Changed in: nova
Status: Fix Committed = Fix Released
** Changed in: nova
Milestone: None = grizzly-2
--
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/1081436
Title:
Only
** Changed in: nova
Status: Fix Committed = Fix Released
** Changed in: nova
Milestone: None = grizzly-2
--
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/1084261
Title:
** No longer affects: lockfile-progs (Ubuntu)
** No longer affects: ntp (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/941968
Title:
lockfile-create hangs inside lxc
Public bug reported:
Also affects genshi 0.6-3 in sid, which should be able to be synced as
the entire Ubuntu delta has been taken up in Debian.
The problem is that raring's python2.7 incorporates changeset
http://hg.python.org/cpython/rev/eb7ea51e658e/ which changed the
definition of
Actually libcgroup no longer ships the init scripts at all. The bug
(recently reported and fixed, not yet SRUd to quantal) was that the init
scripts were not being properly removed.
From the NEWS file:
libcgroup (0.38-1) unstable; urgency=low
This version sees the removal of both
- ubuntu-ec2-run quantal daily --dry-run
--user-data-file=/tmp/my.ud --key=brickies
# us-east-1/ebs/ubuntu-quantal-daily-amd64-server-20130109
euca-run-instances --user-data-file=/tmp/my.ud --key=brickies
--instance-type=t1.micro ami-ed21a884
Then, in console output and /var/log/cloud-init-output.log I
Public bug reported:
In raring, some library functions are returning longs instead of ints.
This is different from behaviour in quantal. This is causing an FTBFS in
genshi due to doctest failures.
Building from upstream source exhibits correct behaviour, including from
upstream orig tarballs and
** Attachment added: slightly simplified version of user-data, should work on
precise also
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1077020/+attachment/3478025/+files/my.ud
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: quantum
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to quantum in Ubuntu.
https://bugs.launchpad.net/bugs/1083387
Title:
failed to update an external network into non
Nice ! Didn't know you could control cloud-init with such precision.
I'll give it a try on my setup and post back.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1077020
Title:
** Changed in: cinder
Status: Fix Committed = Fix Released
** Changed in: cinder
Milestone: None = grizzly-2
--
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/1083818
Title:
** Changed in: quantum
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to quantum in Ubuntu.
https://bugs.launchpad.net/bugs/1083238
Title:
There are routing problems when the dnsmasq port
** Summary changed:
- Quantal does not boot on EC2
+ update-grub-legacy-ec2 ignores kernels named -generic
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1005551
Title:
** Branch linked: lp:~smoser/ubuntu/precise/cloud-init/sru
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1005551
Title:
update-grub-legacy-ec2 ignores kernels named -generic
Second cause of this FTBFS is a possible Python regression in bug
1097783.
** Tags added: ftbfs raring
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to genshi in Ubuntu.
https://bugs.launchpad.net/bugs/1097776
Title:
genshi
Worked great. I can confirm the package in quantal proposed fixed this
issue. Thanks for the fix guys!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1077020
Title:
cloud-init
** Changed in: samba (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/967410
Title:
Windows clients cannot connect to shared printers
** Branch linked: lp:~smoser/ubuntu/precise/cloud-init/sru
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1077020
Title:
cloud-init ca-certs leaves a blank line in
An SRU into existing releases makes good sense. The change is very
minimal, with the biggest risk being that somepoint after the current
operator of D stops using the IP address, said address gets assigned to
someone who decides that giving out the wrong answers would be a thing
to do. I don't
Well after numerous tests, I can no longer reproduce this bug ! I tested
the following :
Precise 12.04.1 VM
Precise 12.04 VM
Quantal 12.10 VM
Quantal 12.10 Baremetal
Raring 13.04 VM
From a vanilla install :
• Confirm Publish shared printers connected to this system is enabled in
@Jon,
I'm not sure how you want to address this - if you consider this a valid
bug (given that the rules engine is flawed and not starting it was by
design) or not. I will mark it invalid, but please feel free to re-mark
it valid if you prefer.
If you'd like to get together for a catchup+design
Public bug reported:
nagios-plugins FTBFS because it embeds an old version of gnulib which
assumes that gets is defined. However, ISO C11 drops the definition.
gnulib upstream have fixed this in
** Bug watch added: SourceForge.net Tracker #3600122
http://sourceforge.net/support/tracker.php?aid=3600122
** Also affects: nagios-plugins via
http://sourceforge.net/support/tracker.php?aid=3600122
Importance: Unknown
Status: Unknown
--
You received this bug notification
** Changed in: samba (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1094438
Title:
Samba crashes invalid pointer: 0x7f0bc3de7590
To
I've uploaded SRU-able versions of the package to my personal ppa. See
https://launchpad.net/~lamont/+archive/ppa/+packages
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1090593
What is the work-around that I might be missing? Trying out juju with
LXC by following https://juju.ubuntu.com/docs/getting-started.html will
make you run directly into this bug. Quite a let-down as everything else
runs so smoothly with juju ...
--
You received this bug notification because you
** Branch linked: lp:~smoser/ubuntu/precise/cloud-init/sru
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1037567
Title:
need config-drive-v2 support
To manage notifications
** Branch linked: lp:~smoser/ubuntu/precise/cloud-init/sru
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1031065
Title:
cloud-init-nonet runs 'start networking' explicitly
To
** Patch added: nagios-plugins.debdiff
https://bugs.launchpad.net/nagios-plugins/+bug/1097848/+attachment/3478295/+files/nagios-plugins.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios-plugins in Ubuntu.
** Attachment added: nagios-plugins_1.4.15-5ubuntu5_amd64.build
https://bugs.launchpad.net/nagios-plugins/+bug/1097848/+attachment/3478296/+files/nagios-plugins_1.4.15-5ubuntu5_amd64.build
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I've checked that this now builds and that a resulting binary
(check_apt) appears to work.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1097848
Title:
nagios-plugins
@Henning,
At one point we thought a workaround was to have devtmpfs mounted in the
container. However that is a bad thing to do as changes in the
container's /dev will be reflected in the host's /dev.
So the only workaround right now (until grub is fixed in precise) is to
check (with 'mount')
Thanks for reporting this bug. The missing file belongs to php5-common
package, which is properly depended upon by libapache2-mod-php5. It
would appear to have been manually deleted. You can cause it to be
reinstalled by doing:
sudo apt-get install --reinstall php5-common
After this, you can
** Changed in: etckeeper (Ubuntu)
Importance: Undecided = Low
** Changed in: bash-completion (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to etckeeper in Ubuntu.
Thanks for reporting this issue.
The logrotate file is a conffile, and per debian policy is only removed
when you purge the package.
sudo apt-get purge squid3
** Changed in: squid3 (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Thanks for submitting this bug.
** Changed in: samba (Ubuntu)
Status: New = Confirmed
** Changed in: samba (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
Thanks for reporting this bug.
I couldn't reproduce this in either precise or raring.
Since you say the solution was to remove /usr/local/bin/glance-*, the
problem appears to have been caused by previous manual installations of
glance - that is, not through the package.
** Changed in: glance
Public bug reported:
in order to use config drive, nova-compute requires genisoimage.
This is fixed in raring's packaging, but not in quantal or precise.
** Affects: nova (Ubuntu)
Importance: Medium
Status: Fix Released
** Affects: nova (Ubuntu Precise)
Importance: Medium
You're welcome. Thank you for taking a look. In ten years, I'd never
encountered a package that, upon removal, left the system in an
erroneous state. I guess I've been lucky.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in
Definitely used in Folsom (and missing as a dep for Quantal) but a quick
grep of the Essex (precise) source doesn't turn up any uses of
genisoimage.
** Changed in: nova (Ubuntu Quantal)
Status: Triaged = Confirmed
--
You received this bug notification because you are a member of Ubuntu
** Branch linked: lp:~gandelman-a/ubuntu/quantal/nova/genisoimage
--
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/1097879
Title:
nova-compute missing dependency on genisoimage
To
** Changed in: asterisk (Debian)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to asterisk in Ubuntu.
https://bugs.launchpad.net/bugs/1097691
Title:
(CVE-2012-5977) AST-2012-015 Denial of Service
** Changed in: asterisk (Debian)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to asterisk in Ubuntu.
https://bugs.launchpad.net/bugs/1097687
Title:
(CVE-2012-5976) AST-2012-014 Crashes due to large
You have been subscribed to a public bug:
For bug 1057024, we have qemu-kvm postinst call udevadm trigger
--action=change. This is to make udev recalculate permissions for
/dev/kvm based on the new /lib/udev/rules.d/40-qemu-kvm.rules file.
In precise, this causes /dev/kvm's acls to be correctly
The cause of the problem is simply the udev-acl call in 70-udev-
acl.rules. Since this is a higher # rule than 40-qemu-kvm.rules, it
gets run after.
The problem can be solved by:
1. moving 40-qemu-kvm.rules to 72-qemu-kvm.rules
2. making qemu-kvm depend on acl
3. appending RUN+=/usr/bin/setfacl
Am 1/8/2013 6:08 PM, Serge Hallyn wrote:
(replying to comment #12) could you please follow up on comments #6 and
#7?
It also would be worthwhile, at this point, checking whether latest
upstream (1.3) is still broken.
Just a short note: I somehow produced a backported *.deb for 1.3.0 and
i
Actually qemu-kvm.rules can stay at 40 by using :=, so the rules file
becomes
KERNEL==kvm, GROUP:=kvm, MODE:=0660, TAG:=,
RUN:=/usr/bin/setfacl -m g::rw /dev/kvm
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
(replacing /dev/kvm with $env{DEVNAME} of course)
--
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/1092715
Title:
udevadm trigger --action=change not working in quantal and raring
Thank You Tang , group 'cinder' already exists.but there is still wrong
--
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/1097548
Title:
can't install cinder-common
To manage
** Branch unlinked: lp:~mathieu-tl/network-manager/0.9.4.0-0ubuntu4.2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1004775
Title:
NetworkManager restarts dnsmasq and adds host
I'm converting this to a wishlist request in line with the Debian bug.
** Changed in: squid3 (Ubuntu)
Importance: Undecided = Wishlist
** Changed in: squid3 (Ubuntu)
Status: Won't Fix = Triaged
** Also affects: squid3 (Debian) via
[Expired for php5 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: php5 (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
** Changed in: squid3 (Debian)
Status: Unknown = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1097032
Title:
Please provide GNUTLS support in squid
To manage
72 matches
Mail list logo
