Ok, let me clarify the situation here: this bug needed to be fixed in
order for the message to disappear and the fix has landed a few days
ago. But there is another bug (bug 1070318) which *also* prevents the
message from being properly removed.
Bug 1068843 is currently being worked on and it
** Branch linked: lp:~julian-edwards/maas/boot_image_messages
** Branch linked: lp:~julian-edwards/maas/nodegroup-on-bootimage-schema-
part2
** Branch linked: lp:~julian-edwards/maas/nodegroup-on-bootimage-schema
--
You received this bug notification because you are a member of Ubuntu
Server
FWIW, this is implemented and works in seabios 0.7.1
--
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/611142
Title:
seabios should have native scsi support
To manage notifications
by default images are expected to be open read-write. I'm against too
much intelligence here, -- we may be running qemu as wrong user, or
with wrong permissions of the image in question, and qemu should fail to
start if the image can't be open using specified access flags (which is
read-write by
There has been numerous reports/wishlists about removing features from
qemu. Different people consider different features to be undesirable.
But this is not how debian/ubuntu works: on these systems, packages are
built with as much as possible features (and hence external
dependencies). If you
** Changed in: maas
Status: Triaged = Fix Released
** Also affects: maas (Ubuntu Quantal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Branch linked: lp:~andreserl/maas/maas_enable_quantal_trunk
** Changed in: maas
Assignee: (unassigned) = Andres Rodriguez (andreserl)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
*** This bug is a security vulnerability ***
Public security bug reported:
A heap-buffer overflow was found in the DKIM DNS decode logic, used by
Exim between version 4.70 and 4.80.
Exim 4.80.1 release announcement:
https://lists.exim.org/lurker/message/20121026.080330.74b9147b.en.html
**
I'm attaching debdiffs for precise and quantal.
** Patch added: exim4_4.76-3ubuntu3.1.debdiff
https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1071694/+attachment/3414225/+files/exim4_4.76-3ubuntu3.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server
** Changed in: exim4 (Ubuntu)
Status: New = Triaged
** Changed in: exim4 (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to exim4 in Ubuntu.
https://bugs.launchpad.net/bugs/1071694
Title:
** Changed in: maas
Status: Fix Released = Confirmed
** Changed in: maas
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1069850
Title:
** Also affects: maas/1.2
Importance: Undecided
Status: New
** Changed in: maas
Milestone: 12.10-stabilization = None
** Changed in: maas/1.2
Milestone: None = 12.10-stabilization
** Changed in: maas/1.2
Status: New = Triaged
** Changed in: maas/1.2
Importance:
** Also affects: maas/1.2
Importance: Undecided
Status: New
** Changed in: maas/1.2
Milestone: None = 12.10-stabilization
** Changed in: maas
Milestone: 12.10-stabilization = None
** Changed in: maas/1.2
Status: New = Incomplete
** Changed in: maas
Status:
** Also affects: maas/1.2
Importance: Undecided
Status: New
** Changed in: maas/1.2
Milestone: None = 12.10-stabilization
** Changed in: maas
Milestone: 12.10-stabilization = None
** Changed in: maas/1.2
Status: New = Triaged
** Changed in: maas/1.2
Importance:
** Also affects: maas/1.2
Importance: Undecided
Status: New
** Changed in: maas/1.2
Status: New = Triaged
** Changed in: maas/1.2
Importance: Undecided = Low
** Changed in: maas/1.2
Milestone: None = 12.10-stabilization
** Changed in: maas
Milestone:
** Also affects: maas/1.2
Importance: Undecided
Status: New
** Changed in: maas/1.2
Milestone: None = 12.10-stabilization
** Changed in: maas
Milestone: 12.10-stabilization = None
** Changed in: maas/1.2
Status: New = Fix Committed
** Changed in: maas/1.2
Updates have already been published.
** Changed in: exim4 (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to exim4 in Ubuntu.
https://bugs.launchpad.net/bugs/1071694
Title:
CVE-2012-5671:
This bug was fixed in the package apparmor - 2.7.102-0ubuntu3.4
---
apparmor (2.7.102-0ubuntu3.4) precise-security; urgency=low
* debian/debhelper/postrm.apparmor: do not delete local files if main
conffile still exists since it probably means it is owned by a
new/different
Hm, I'm getting:
error: unrecognized arguments: --availability-zone
Try `nova' for more information.
I'm running Essex. Is this a Folsom-only option? No way to get around it
in Essex?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
The way to check upstream qemu's git HEAD is:
sudo apt-get build-dep qemu-kvm
sudo apt-get install git
git clone git://git.qemu.org/qemu.git
cd qemu
./configure --target-list=x86_64-softmmu
make
then run it as
cd x86_64-softmmu
./qemu-system-x86_64 --enable-kvm
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
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
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
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
Thanks, Davide, cann you tell us the paths of the snapshot files which
need to be whitelisted?
--
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/1004606
Title:
virsh create-snapshot
Public bug reported:
The upgrade failed because the mysql database had a root password and the
script used to update the db tries to do it with an empty password. I did the
update manually using the script /usr/share/bacula-director/update_mysql_tables
which I had to modify because it is
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in Ubuntu.
https://bugs.launchpad.net/bugs/1071756
Title:
package bacula-director-mysql 5.2.5-0ubuntu6.2 [modified: usr/share
stgraber suggests this may be due to devtmpfs being mounted in the
container - can you show the result of
cat /var/lib/lxc/q1/fstab
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Changed in: maas (Ubuntu Precise)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1067929
Title:
maas-region-celeryd connects to the wrong queue.
** Changed in: maas (Ubuntu Precise)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1067261
Title:
Web reference in UI points to wrong place
To
** Changed in: maas (Ubuntu Precise)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1064638
Title:
Commissioning is failing to set node memory
apport information
** Tags added: apparmor apport-collected quantal
** Description changed:
I tried to use juju in local environment (it uses lxc in this case). But
getting started guide didn't work for me. In the end I was suggested to
execute couple of commands from console and file a
apport information
** Attachment added: KernLog.txt
https://bugs.launchpad.net/bugs/1071504/+attachment/3414377/+files/KernLog.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Changed in: maas (Ubuntu Precise)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1064672
Title:
Node listing page becomes unusable with increased
** Changed in: maas (Ubuntu Precise)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1066938
Title:
maas-dns changes default bind rndc key and breaks
** Changed in: maas (Ubuntu Precise)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1066929
Title:
duplicate entry added to named.conf.local on each
I have performed following command locally - apport-collect 1071504. As
I understand, results should be available for you now.
Also I tried to execute sudo lxc-start -n q1 -l debug -o outout1 once
again and now it prompted to log in (I have no idea what login/password
to put there). outout1 is in
The path, excluding extension, is the same as the original image.
Unfortunately the extension can be chosen by the user:
Name
The name for this snapshot. If the name is specified when initially creating
the snapshot, then the snapshot will have that particular name. If the name
is omitted
** Summary changed:
- Version bump request to 2.0.6+
+ Please merge libapache2-mod-perl2
** Changed in: libapache2-mod-perl2 (Ubuntu)
Status: New = Triaged
** Changed in: libapache2-mod-perl2 (Ubuntu)
Importance: Undecided = Wishlist
--
You received this bug notification because you
This problem has resurfaced in tomcat7 with identical symptoms. The
simplest fix is to use the new tomcat connection pool.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat6 in Ubuntu.
https://bugs.launchpad.net/bugs/283852
Hello andrew, or anyone else affected,
Accepted bridge-utils into precise-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/bridge-
utils/1.5-2ubuntu7 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Public bug reported:
The default DataSource factory in tomcat 7 (and previously in tomcat6)
is org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory. This is contained
in a jar file which the Debian maintainers don't distribute. The same
problem also affected tomcat6:
Public bug reported:
The current 'common', 'server' and 'shared' subdirectories are not
documented in tomcat7 where a single 'lib' directory might be expected.
This is confusing if you never used tomcat5 or earlier. Please either
change the directories to match the documentation or add something
*** This bug is a duplicate of bug 1070914 ***
https://bugs.launchpad.net/bugs/1070914
I have installed lxc packages from quantal-proposed, but still have same
problem with juju. All units are pending. Any thoughts?
--
You received this bug notification because you are a member of Ubuntu
Probably apparmor is blocking the executable.
in /var/log/apport.log I can see the line:
ERROR: apport (pid 4224) Fri Oct 26 22:29:35 2012: executable does not belong
to a package, ignoring
When copying qemu-system-x86_64 into /usr/bin
and executing within that directory ( ./qemu-system-x86_64
Could you please post the script which triggers this?
Note that you shouldn't need to manually mount and umount the lvm
partitions. If you've create the container with either 'lxc-create -t
ubuntu -B lvm -n q1' or 'lxc-clone -s -o q1 -n q2', then you can simply
'lxc-start -n q1' (or q2) to start
I hadn't noticed this before:
[ 761.143056] [ cut here ]
[ 761.143064] WARNING: at /build/buildd/linux-3.5.0/kernel/irq/manage.c:436
__enable_irq+0x3b/0xd0()
[ 761.143066] Hardware name: To be filled by O.E.M.
[ 761.143067] Unbalanced enable for IRQ 41
[ 761.143068]
Thanks, Gerben. If it were possible for you to run it by hand that
would be easier. But to do it through libvirt without a package becomes
more complicated. To undo your changes (in particular copying the qemu-
system-x86_64 into /usr/bin), please do
sudo apt-get install --reinstall qemu-kvm
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
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/1071011
Title:
specific device not available in client (passthrough)
** Tags added: apparmor
--
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/1004606
Title:
virsh create-snapshot fails to create external snapshot (blockdev-
snapshot-sync fails in
50 matches
Mail list logo
