Public bug reported:
Had been using lxc on a laptop. Nothing unusual - basic LXC experiments,
created and removed several containers. Suspended and resumed the laptop
at least 5 times between last using lxc and the lxc upgrade.
Perhaps one or more containers is still active?
ProblemType:
--
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/1033412
Title:
package lxc 0.7.5-3ubuntu60 failed to install/upgrade: unable to
install new version of `/usr/lib/lxc/liblxc.so.0.7.5':
** Tags removed: need-duplicate-check
--
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/1033412
Title:
package lxc 0.7.5-3ubuntu60 failed to install/upgrade: unable to
install new
@peter
I have change the filter and update into new init ram disk, thanks.
For powerpath issue, i reproduce by shutdown FC switch port. Here is new
complete syslog of whole prodefure and multipath result.
1)multipath_before_port_down -- multipath status before shutdown port
** Also affects: percona-server/5.1
Importance: Undecided
Status: New
** Also affects: percona-server/5.5
Importance: Medium
Status: New
** Changed in: percona-server/5.1
Assignee: (unassigned) = Ignacio Nin (ignacio-nin)
** Changed in: percona-server/5.5
Assignee:
** Changed in: net-snmp (Ubuntu)
Status: Opinion = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to net-snmp in Ubuntu.
https://bugs.launchpad.net/bugs/659376
Title:
mibs absent from maverick
To manage notifications
Public bug reported:
When I try to delete an IP that is attached to a server, it is only
removed from the server, but not deleted. Only the second delete will
actually delete it. I waited several seconds between the commands. I
expect the command to either fail completely or remove the IP from
Okay, I finally took the time to get a backtrace. It seems that it only
takes a few minutes before smbd crashes, I wonder how many tmes it
crahes before apport catches.
Btw, I'm running the Quantal Alpha, and smbd crashes the same as it did
in Precise.
** Attachment added: gdb-smbd.txt
** Changed in: samba (Ubuntu)
Status: Incomplete = New
--
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/913809
Title:
smbd crashed with SIGABRT in rep_strlcpy()
To manage
** Changed in: samba (Debian)
Status: Unknown = Confirmed
--
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/1032133
Title:
smbclient fails if server does not support Echo
Is this a suitable upstream fix/workaround?
http://git.kernel.org/?p=linux/storage/autofs/autofs.git;a=commitdiff;h=b8e06337764df00b30901c7787e0d1861c2f9901
** Changed in: autofs5 (Ubuntu)
Status: Confirmed = Triaged
** Changed in: autofs5 (Ubuntu Precise)
Status: Confirmed =
** Changed in: cloud-init (Ubuntu)
Importance: Undecided = Medium
** Changed in: cloud-init (Ubuntu)
Status: New = Triaged
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) = Scott Moser (smoser)
--
You received this bug notification because you are a member of Ubuntu
You have been subscribed to a public bug:
Had been using lxc on a laptop. Nothing unusual - basic LXC experiments,
created and removed several containers. Suspended and resumed the laptop
at least 5 times between last using lxc and the lxc upgrade.
Perhaps one or more containers is still active?
Moving the bug to dpkg as lxc isn't doing anything weird that'd explain this.
Replacing a file currently in use is perfectly possible on Linux and shouldn't
cause that error.
** Package changed: lxc (Ubuntu) = dpkg (Ubuntu)
--
You received this bug notification because you are a member of
07:27 infinity stgraber: That's not a dpkg bug, can I bounce it back? :P
07:28 infinity stgraber: dpkg is trying to write to the file and failing,
it's not up to dpkg to
ensure the world is writable.
07:28 infinity stgraber: I'd assume this is either lxc userspace being
Please attach:
- ls -l /usr/lib/lxc/liblxc.so.0.7.5
- sudo lsof -n
** Changed in: lxc (Ubuntu)
Status: New = Incomplete
--
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/1033412
** Also affects: cloud-init (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu Precise)
Importance: Undecided = Medium
** Changed in: cloud-init (Ubuntu Precise)
Status: New = Triaged
** Changed in: cloud-init (Ubuntu Precise)
Assignee:
** Changed in: lxc (Ubuntu)
Importance: Undecided = High
** Changed in: lxc (Ubuntu)
Status: New = Triaged
** Changed in: lxc (Ubuntu)
Importance: High = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in
Is this hardware that did work before or new hardware?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ipmitool in Ubuntu.
https://bugs.launchpad.net/bugs/1032724
Title:
Cannot access IPMI card
To manage notifications about this
This is fixed in cloud-init trunk and in the ubuntu quantal package listed in
comment 4.
I've tested this by:
* setup:
* have *some* way to add 'ubuntu-mirror' to the dns for kvm guests
I used dnsmasq on a server system, and can control this by adding entries
to /etc/hosts. You
Is nova-cert installed and running ?
** Changed in: nova
Status: New = Incomplete
--
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/1031021
Title:
nova x509-create-cert times out
$ virsh define /tmp/foo.xml
error: Failed to define domain from /tmp/foo.xml
error: internal error no supported architecture for os type 'hvm'
This means that libvirt can't find any way to provide the requested domain
configuration. Since your XML shows you requested KVM, most likely this
Actually, second question: was ipmitool run as root, too? The /dev/ipmi0
file is only readable by root.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ipmitool in Ubuntu.
https://bugs.launchpad.net/bugs/1032724
Title:
Cannot access
Ok, stupid question as it seems to be obvious from the login prompt,
sorry. Tried this on my machine and it did work, though.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ipmitool in Ubuntu.
https://bugs.launchpad.net/bugs/1032724
Thanks for the patch. This can definately be applied to quantal and
precise.
** Changed in: vm-builder (Ubuntu)
Status: Confirmed = Triaged
** Also affects: vm-builder (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: vm-builder (Ubuntu Quantal)
One thing I saw in the dmesg: the io memory (0xca8) which the SMBIOS
returns is not registered/reserved before. On my machine there is a
reservation by one of the ACPI PNP devices (PNP0c02).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
So this seems to cause some errors later and no BMC in found, thus no
device /dev/ipmi0 is created.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ipmitool in Ubuntu.
https://bugs.launchpad.net/bugs/1032724
Title:
Cannot access
Blueprint changed by Serge Hallyn:
Work items changed:
Work items:
[stgraber] Review list of extra packages in lxc-ubuntu and have it contain
the right list for each release: DONE
[cooloney] check that all new cgroups are enabled in quantal kernel: DONE
[serge-hallyn] pre-mount cgroups
Blueprint changed by Serge Hallyn:
Work items changed:
Work items:
[smoser] jump for joy: DONE
[rbasak] follow up on console log size limit implementation (ringbuffer): TODO
[stefan-bader-canonical] confirm the xen and qemu prom naming is correct
after the debian merge back (look ok):
Blueprint changed by Serge Hallyn:
Whiteboard changed:
Etherpad: http://pad.ubuntu.com/uds-q-servercloud-q-kvm
Blueprint: https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-kvm
User Stories:
N/A
Assumptions:
None
Release Notes:
None
+
+ Development Notes:
No it was not. Somehow I had it installed in my 12.04 install even
though it has no reverse dependencies in precise either. I've updated
the instructions for our setup. Feel free to close this bug.
** Changed in: nova (Ubuntu)
Status: New = Invalid
--
You received this bug notification
(Fix confirmed, the test case I'm using is:
sudo vmbuilder kvm ubuntu -o -v --tmpfs 1536 --rootsize=4096M
--swapsize=512M -d vm1 --proxy=http://localhost:3142
)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
** Tags added: rls-q-incoming
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/974450
Title:
irqbalance classifies network interfaces with custom/renamed
interfaces as class
This bug was fixed in the package vm-builder - 0.12.4+bzr481-0ubuntu1
---
vm-builder (0.12.4+bzr481-0ubuntu1) quantal; urgency=low
[ Yoann Dubreuil ]
* Fix proxy support: set up apt proxies before writing sources.list.
(LP: #966944)
-- Serge Hallyn serge.hal...@ubuntu.com
** Branch linked: lp:~openstack-ubuntu-testing/nova/precise-folsom
--
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/1002111
Title:
iptables being run on a nova-api server
To manage
** Description changed:
+
+ SRU Justification:
+ 1. impact: creating VMs using an apt proxy fails
+ 2. Development fix: set up apt proxies before creating sources.list
+ 3. Stable fix: same as development fix
+ 4. Test case:
+ sudo apt-get -y install
Hi Stefan,
These are HP ProLiant MicroServer Remote Access Card's (I have 3 HP
Micro Servers with these cards). If you want access to them to debug I
could give it to you!
Cheers.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Branch linked: lp:ubuntu/vm-builder
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/966944
Title:
proxy support not fully working
To manage notifications about this bug go
** Also affects: vm-builder (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: vm-builder (Ubuntu Precise)
Importance: Undecided = High
** Changed in: vm-builder (Ubuntu Precise)
Status: New = Triaged
** Changed in: vm-builder (Ubuntu Precise)
Assignee:
** Changed in: php5 (Ubuntu)
Assignee: (unassigned) = Thomas Ward (trekcaptainusa-tw)
** Changed in: php5 (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
** Description changed:
+ ===
+ SRU Justification:
+ 1. Impact: simple vm creations fail
+ 2. Development fix: use dpkg-divert to replace initctl with our stub, so that
when usptart is installed it does not replace it with the real one
+ 3. Stable fix: same as
Attached is a Quantal debdiff, based off of Quantal package
php5_5.4.4-3ubuntu1.
** Patch added: Quantal debdiff with Upstream Patch for LP #1006738
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1006738/+attachment/3250571/+files/quantal_lp1006738.debdiff
--
You received this bug
** Changed in: php5 (Ubuntu)
Status: In Progress = Opinion
** Changed in: php5 (Ubuntu)
Status: Opinion = Triaged
** Changed in: php5 (Ubuntu)
Assignee: Thomas Ward (trekcaptainusa-tw) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
** Branch linked: lp:~openstack-ubuntu-testing/keystone/quantal-folsom-
proposed
--
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/1029766
Title:
keystone logrotate has output when
Hey Sam-
Thanks for the patch. I've merged the change into our -proposed
packaging branches, where the change will be incorporated into our CI
builds (available in ppa:openstack-ubuntu-testing/folsom-trunk-testing)
and be merged to ~ubuntu-server-dev branch (and Ubuntu archive) with the
next
On initial investigation of the given patch, it seemed that this problem
would be fairly easy to solve with a cherry picked patch.
But, this is not so. ipAddress and privateIpAddress were not present in
the default version of the EC2 API that txaws supported in the release
shipped in precise (EC2
Also attaching some test code I wrote to show where ip_address will or
will not appear as a valid attribute depending on the version of txaws.
If the patch is cherry picked, the ipaddress shows up, but
terminateInstances raises an error because of the missing shutdownState.
** Attachment added:
Attaching successful no-change source rebuild on precise of quantal
version.
** Attachment added: txaws_0.2.3-1ubuntu1_amd64-20120806-1629.build
https://bugs.launchpad.net/precise-backports/+bug/945176/+attachment/3250690/+files/txaws_0.2.3-1ubuntu1_amd64-20120806-1629.build
--
You received
This is the output of the test program. Note that the backtrace about
NoneType is normal (coding error due to my ignorance of how to do things
perfectly in twisted).
$ python test-txaws-ipaddress.py ami-9666e9a6
i-e5269ad6
Mon Aug 6 16:32:33 2012: polling ec2...
Mon Aug 6 16:32:33 2012:
Testing juju (only rdep of python-txaws) with backported txaws, works
perfectly:
Setting up juju (0.5+bzr531-0ubuntu1.2) ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
(precise-amd64)root@clint-MacBookPro:/home/clint/pkg/txaws/backport# su - clint
Also tested backported aws-status, which is an indicator built on top of
txaws. Works fine in precise.
** Changed in: precise-backports
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to txaws in Ubuntu.
build log of juju from precise building with backported txaws
** Attachment added: buildlog-juju-precise-backported-txaws.txt
https://bugs.launchpad.net/ubuntu/precise/+source/txaws/+bug/945176/+attachment/3250699/+files/buildlog-juju-precise-backported-txaws.txt
--
You received this bug
Public bug reported:
Please sync whois 5.0.18 (main) from Debian unstable (main)
Changelog entries since current quantal version 5.0.17:
whois (5.0.18) unstable; urgency=low
* Updated the .ae and .xn--mgbaam7a8h (.امارات, United Arabs Emirates)
TLDs.
* Updated the server charset table
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: whois (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to whois in Ubuntu.
https://bugs.launchpad.net/bugs/967311
+1 for PHP 5.4 in precise-backports. Does that require a new bug to be
filed to keep track of?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/948156
Title:
Please merge PHP 5.4 from
The attachment Quantal debdiff with Upstream Patch for LP #1006738 of
this bug report has been identified as being a patch in the form of a
debdiff. The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff. In the event
that this is
This looks good, uploading based on feedback from SpamapS on IRC.
** Changed in: precise-backports
Status: Confirmed = In Progress
** Changed in: precise-backports
Assignee: (unassigned) = Micah Gersten (micahg)
--
You received this bug notification because you are a member of
This has been accepted into precise-backports.
** Changed in: precise-backports
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to txaws in Ubuntu.
https://bugs.launchpad.net/bugs/945176
Title:
The verification of this Stable Release Update has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression
Seems like it's without controversy to release the lucid SRU, so I've
done that.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in Ubuntu.
https://bugs.launchpad.net/bugs/569757
Title:
NIS upstart dependency broken for lucid
This bug was fixed in the package nis - 3.17-31ubuntu0.10.04.3
---
nis (3.17-31ubuntu0.10.04.3) lucid-proposed; urgency=low
* debian/nis.ypbind.upstart: don't try to start ypserv if
NISSERVER=false.
nis (3.17-31ubuntu0.10.04.2) lucid-proposed; urgency=low
* Drop the upstart
The verification of this Stable Release Update has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression
This bug was fixed in the package amavisd-new - 1:2.6.5-0ubuntu3.2
---
amavisd-new (1:2.6.5-0ubuntu3.2) precise-proposed; urgency=low
* Replace incorrect parameter 'spf-policyd_time_limit' with a
correct 'policy-spf_time_limit' (LP: #996569)
-- Ante Karamatic iv...@ubuntu.com
[Expired for samba (Ubuntu) because there has been no activity for 60
days.]
** Changed in: samba (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
[Expired for samba (Ubuntu) because there has been no activity for 60
days.]
** Changed in: samba (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
[Expired for bind9 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: bind9 (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
66 matches
Mail list logo
