I think the blueprint https://blueprints.launchpad.net/nova/+spec
/serial-ports is just a workaround for this bug, and currently we have
no way to disable console.log .
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
Public bug reported:
I'm trying to migrate an OS running on a physical machine to an LXC container,
but no luck so far. Right now the system gets stuck somewhere during lxc-start:
...
* Stopping cgroup management proxy ...done.
* Starting load modules from /etc/modules ...done.
*
Well, today is Oct 8th 2014 and I just lost three VMs because of this.
That the tyrget folder (/var/lib/libvirt/images) wasn't backed-up is my
fault but the documentation SHOULD BE CLEARER about what happens when
you pass the -o option to vmbuilder.
And yes, overwriting the whole directory is
Blueprint changed by James Page:
Work items changed:
Work items for ubuntu-14.05:
[gnuoy] charm-helpers unit testing: DONE
Work items for ubuntu-14.06:
[mikemc] Simplestreams image sync charm: DONE
[niedbalski] swift-storage block device persistence through reboots: DONE
[gnuoy]
There does not seem to be clear documentation on this. Just a note that from
your description I was not completely sure whether you did unmount before
starting the release procedure. I would say unmount is a must.
Doing so, I also ended up in the state where bcache0 still existed. But I was
+1 on the fail to reproduce. Followed the steps and everything worked
without issues (using kvm/qemu VM with emulated devices and even sda
being backed by a real ssd, but I am not sure the difference gets
propagated).
--
You received this bug notification because you are a member of Ubuntu
** Changed in: python-eventlet (Ubuntu)
Importance: Undecided = High
** Changed in: python-eventlet (Ubuntu)
Milestone: None = ubuntu-14.10
** Also affects: python-eventlet (Ubuntu Utopic)
Importance: High
Status: Triaged
--
You received this bug notification because you are a
In fact whether you unmount before stopping the bcache or not doesn't
change the behaviour. I did that this way in the description, to show
the process. You just stop the caching device with the echo 1 ...
But, the backing is still in use, but you have no control over it.
Le 08/10/2014 13:15,
Yes you can get rid of bcache0, but you can't re-use the device for
anything unless you reboot ( re bcache or just plain fdisk/parted ).
Le 08/10/2014 13:15, Stefan Bader a écrit :
There does not seem to be clear documentation on this. Just a note that from
your description I was not
Yes you can get rid of bcache0, but you can't re-use the device for
anything unless you reboot ( re bcache or just plain fdisk/parted ).
In fact whether you unmount before stopping the bcache or not doesn't change
the behaviour. I did that this way in the description, to show the process.
You
Strange, I can reproduce each time, I'm using the iso:
ubuntu-14.10-beta2-desktop-amd64.iso from http://releases.ubuntu.com/utopic/
I'm on utopic, with vrit-manager.
Regards.
Le 08/10/2014 13:17, Stefan Bader a écrit :
+1 on the fail to reproduce. Followed the steps and everything worked
Public bug reported:
==
FAIL: test_COPY_account_source_larger_than_max_file_size
(test.unit.proxy.test_mem_server.TestObjectController)
--
Traceback (most
Public bug reported:
Symbols file mismatch: https://launchpad.net/ubuntu/+archive/test-
rebuild-20140914/+build/6371580/+files/buildlog_ubuntu-
utopic-i386.libecap_0.2.0-1ubuntu4_FAILEDTOBUILD.txt.gz
The attached patch fixes it, but I'm not comfortable uploading since I
don't see how I can
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Changed in: maas (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Changed in: libecap (Ubuntu)
Status: Triaged = In Progress
** Changed in: libecap (Ubuntu)
Assignee: (unassigned) = Robie Basak (racb)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libecap in Ubuntu.
Public bug reported:
The latest libelf removed DW_TAG_mutable_type in upstream commit
af1e6ed9b4c0160a6a5c6f59d9443ae4f6f20a14, causing an FTBFS on Utopic
(Trusty still builds).
** Affects: dwarves-dfsg (Ubuntu)
Importance: Undecided
Assignee: Robie Basak (racb)
Status: In
** Also affects: swift
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to swift in Ubuntu.
https://bugs.launchpad.net/bugs/1378810
Title:
swift unit tests fail on i386 buildd
To manage
13:53 rbasak doko: sorry, I'm still not comfortable with this. I don't really
follow the bigger picture of how to determine that these symbols really aren't n
eeded.
13:53 rbasak The package includes all the headers, which makes it
awkward.
13:54 rbasak doko: if you're happy with my diff, then
Hm, it was helping in my case. So here from my re-run with utopic KVM
host:
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:00 16G 0 disk
└─bcache0 251:008G 0 disk /mnt
sdb 8:16 08G 0 disk
└─bcache0 251:008G 0 disk /mnt
#
** Bug watch added: Debian Bug tracker #764484
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764484
** Also affects: dwarves-dfsg (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764484
Importance: Unknown
Status: Unknown
--
You received this bug notification
# umount /mnt
# echo 1 /sys/fs/bcache/a8f70bd1-48df-462f-9a2c-ca4b8af9059c/unregister
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:00 16G 0 disk
sdb 8:16 08G 0 disk
└─bcache0 251:008G 0 disk
# echo 1 /sys/block/bcache0/bcache/stop
# lsblk
Interesting note: echo 1 /sys/block/bcache0/bcache/stop from a point
where the bcache is registered and running (but not mounted) directly
releases both devices for me.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bcache-tools in
which can be fixed by unregistering via /sys/fs/bcache... what a
horrible interface.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bcache-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1377142
Title:
Bcache doesn't allow full
Ok, but that leaves sda in a state which looks unclaimed but is still in
use.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bcache-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1377142
Title:
Bcache doesn't allow full
Thanks for reporting this bug. To fix the cgmanager issue, add the line
lxc.mount.auto = cgroup:mixed
to your container configuration file.
That shouldn't explain your hang however. Assuming it doesn't, please
run
lxc-start -n container -l trace -o debug.out -- /sbin/init debug
verbose
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pm-utils (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pm-utils in Ubuntu.
Thanks,
I didn't wrote to /sys/block/bcache0/bcache/stop, I missed this as I was
only looking in /dev/bcache* and in /sys/fs/bcache; which explains why I
was left with an used device.
I agree that the interface is not very user-fiendly, we may need to
improve the bcache-tools command to simplify
You have been subscribed to a public bug:
I first reported this issue on the Dovecot mailing list, but nobody
there was able to help me identify the source of the problem (no less
how to fix it). And that's a pretty sharp group! Here's the full thread:
** Package changed: ubuntu = dovecot (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in Ubuntu.
https://bugs.launchpad.net/bugs/1378446
Title:
dovecot-lda crashes (exits with status code 134) when message is
** Tags added: cts
--
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/1310629
Title:
Nova configuration template has deprecated items ( grizzly )
To manage notifications about this bug
** Branch linked: lp:~ubuntu-branches/ubuntu/utopic/libecap/utopic-
proposed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libecap in Ubuntu.
https://bugs.launchpad.net/bugs/1378819
Title:
FTBFS on Utopic, all architectures
To
This bug was fixed in the package dwarves-dfsg - 1.10-2ubuntu1
---
dwarves-dfsg (1.10-2ubuntu1) utopic; urgency=medium
* d/p/DW_TAG_mutable_type: fix FTBFS due to newer elfutils
(LP: #1378841).
-- Robie Basak robie.ba...@ubuntu.com Wed, 08 Oct 2014 14:05:27 +
** Changed
** Branch linked: lp:debian/haproxy
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to haproxy in Ubuntu.
https://bugs.launchpad.net/bugs/1038139
Title:
Missing running check on init script
To manage notifications about this bug go
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libecap in Ubuntu.
https://bugs.launchpad.net/bugs/1378819
Title:
FTBFS on Utopic, all architectures
To manage notifications about this bug go to:
Michael
After some discussion with contributors to this project and within the
Ubuntu Server team, I'm withdrawing this MIR for now; I'm not happy that
enough QA goes on upstream prior to releases - the broken test suite is
just one symptom of this.
For now, we will skip the websockify dependent
@Andres: A debdiff from utopic to utopic might have been easier to
review than the 7MB (!) diff from trusty. :P
--
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/1370628
Title:
[FFe]
I'm not convinced the two FFes are actually tied to each other, but some
confirmation from the MaaS team would be nice.
ie: I don't see why this new MaaS version would suddenly be more or less
broken with or without the psycopg2 change.
--
You received this bug notification because you are a
This bug was fixed in the package libecap - 0.2.0-1ubuntu5
---
libecap (0.2.0-1ubuntu5) utopic; urgency=medium
* d/libecap2.symbols: mark four more symbols optional to fix FTBFS, as
these don't appear to form part of the formal ABI but have
disappeared (LP: #1378819).
--
He he oops! I'll attach one once o get my hands to a computer!
On Oct 8, 2014 6:45 PM, Adam Conrad adcon...@0c3.net wrote:
@Andres: A debdiff from utopic to utopic might have been easier to
review than the 7MB (!) diff from trusty. :P
--
You received this bug notification because you are
Public bug reported:
On ubuntu 14.04 instaled MariaDb 5.5. Mysql server 5.6 install returned
this error
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: mysql-server-5.6 (not installed)
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Uname: Linux 3.13.0-36-generic x86_64
These two FFe's are not tied together. The psycopg issue only affects MAAS
by preventing it from uploading large objects to the database (larger than
2gb). In MAAS terms it prevents from uploading OS images larger than 2gb,
that don't affect Ubuntu deployments, but do affect third part OS image
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1378955
Title:
package mysql-server-5.6 (not installed) failed to install/upgrade:
** Changed in: walinuxagent (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to walinuxagent in Ubuntu.
https://bugs.launchpad.net/bugs/1375252
Title:
Hostname change is not preserved across
On Wednesday, October 08, 2014 17:28:13 you wrote:
These two FFe's are not tied together. The psycopg issue only affects MAAS
by preventing it from uploading large objects to the database (larger than
2gb). In MAAS terms it prevents from uploading OS images larger than 2gb,
that don't affect
Just adding more griping :) would be nice to see this fixed in Trusty
sometime before next February
bladernr@klaatu:~$ ftp transit
Connected to transit.lanes.
220 (vsFTPd 3.0.2)
Name (transit:bladernr): bladernr
331 Please specify the password.
Password:
no talloc stackframe at
Public bug reported:
I'm using the Python API to append entries to the LXC config file. When
I do the following:
container.set_config_item(lxc.mount.auto, cgroup:mixed)
I get an extra lxc.mount.auto entry in the config file. This is what it
looks like:
lxc.mount.auto =
lxc.mount.auto =
** Changed in: libvirt (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1324393
Title:
Force off fails with Permission denied after
I advise against backporting apparmor and suggest you simply adjust
debian/rules to filter out the offending rules or to ship a different
profile.
** Changed in: apparmor (Ubuntu)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
** Changed in: apparmor (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in Ubuntu.
https://bugs.launchpad.net/bugs/997269
Title:
dovecot imap broken by apparmor policy
To
Thanks for submitting this bug
status: confirmed
importance: high
** Changed in: lxc (Ubuntu)
Importance: Undecided = High
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
You have been subscribed to a public bug:
-- Problem Description --
irqbalance is not working properly in Ubuntu 14.04.1, all the interrupts are
going exclusively to one CPU instead of being spread.
# service irqbalance status
irqbalance start/running, process 832
# cat /proc/interrupts |
Fix proposed to branch: master
Review: https://review.openstack.org/127082
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1323729
Title:
Remove Open vSwitch and Linuxbridge plugins
** Package changed: ubuntu = irqbalance (Ubuntu)
--
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/1379065
Title:
Ubuntu 14.04.1: irqbalance not working
To manage notifications
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin1404
--
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/1379065
Title:
Ubuntu 14.04.1: irqbalance not
Public bug reported:
The update-grub-legacy-ec2 script (which ships with grub-legacy-ec2,
which is presumably included under cloud-init umbrella) includes a check
to determine whether a kernel is Xen-capable or not. It uses this check
in a feature designed to ignore non-Xen kernels on Xen guests,
The re-compile by Robert also requires you to enable the module with
apache2 at the end.
# a2enmod wsgi
# service apache2 restart
# ls -lah /etc/apache2/mods-enabled/
lrwxrwxrwx 1 root root 27 Oct 9 02:57 wsgi.conf -
../mods-available/wsgi.conf
lrwxrwxrwx 1 root root 27 Oct 9 02:57
Public bug reported:
all versions
The default cipher for openvpn is BF-CBC (blowfish), which was likely
once a good choice.
Virtually all modern hardware has hardware acceleration/support for AES
instructions, and can therefore do AES-128-CBC far faster and more
efficiently than it can
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openvpn (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvpn in Ubuntu.
I just got this by building my own package against trunk using the trunk
packaging.
--
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/1379144
Title:
maas-proxy package won't install when
Public bug reported:
Snippet from the terminal:
Selecting previously unselected package maas-proxy.
dpkg: regarding maas-proxy_1.7.0~beta4+bzr3127-0ubuntu1_all.deb containing
maas-proxy:
maas-proxy breaks squid-deb-proxy
squid-deb-proxy (version 0.8.6) is present and installed.
dpkg: error
Tagging Andres!
--
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/1379144
Title:
maas-proxy package won't install when upgrading from older version
To manage notifications about this
** Changed in: nova (Ubuntu)
Status: In Progress = Confirmed
** Changed in: nova (Ubuntu)
Assignee: Kanchan Gupta (kanchan-gupta1) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
62 matches
Mail list logo
