Public bug reported:
As we can see from bug 978297.
In precise, apparmor doesn't start in a container.
So in debian/maas-dhcp.postinst and debian/maas-dhcp.postinst, we should
not call the apparmor_parser command in a container.
/bin/running-in-container is used in /etc/init.d/apparmor to fin
*** This bug is a duplicate of bug 1033727 ***
https://bugs.launchpad.net/bugs/1033727
This maybe not a duplicate as we're using 1.3.1 and Windows 7 isn't
working there either. All other Operating systems are working though.
@Wessel: I believe the bug you pointed out as duplicate is saying th
Bryan, have you tried following the step-by-step instructions at
maas.ubuntu.com at all?
--
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/975472
Title:
add high level design document(s)
** Branch linked: lp:~ubuntu-server-dev/nova/havana
--
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/1197119
Title:
nova-spiceproxy requires spice-html5
To manage notifications about th
** Branch linked: lp:~ubuntu-server-dev/nova/havana
--
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/1197163
Title:
nova-xvpvncproxy installs no upstart job
To manage notifications abou
Yeah would be nice to know how this thing works. I have never been able
to get MAAS to work... EVER
In comparison and contrast I have used Dell Crowbar and can PXE
provision ubuntu nodes all day long.
Bryan
--
You received this bug notification because you are a member of Ubuntu
Server Team, wh
There is at least one fundamental bug in start.c's signal_handler, as should
be fixed by the below. However, this alone did not fix it for me, so more is
wrong. There is a minimal testcase at
http://people.canonical.com/~serge/signalfd.c which originally reproduced this
bug, then was fixed by
Marking invalid as I couldn't reproduce, and IIUC you will re-try with
fresh containers.
If you run into this again, please re-mark it new and do a 'apport-
collect 1196518'.
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member
Override component to main
python-amqp 1.0.12-0ubuntu1 in saucy: universe/python -> main
python-amqp 1.0.12-0ubuntu1 in saucy amd64: universe/python/optional/100% ->
main
python-amqp 1.0.12-0ubuntu1 in saucy armhf: universe/python/optional/100% ->
main
python-amqp 1.0.12-0ubuntu1 in saucy i386: u
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.10 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
** 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1196295
Title:
lxc-start enters uninterruptible sleep
To manage notificatio
Blueprint changed by Stefan Bader:
Work items changed:
Work items:
[ebiederm] Push fix for XFS and user namespaces: TODO
[serge-hallyn] Fix lxc-net to be nestable with no user interaction: DONE
[serge-hallyn] Write sysctl to disable unprivileged CLONE_NEWUSER: DONE
[serge-hallyn] Exploit
multipath-tools will grab any devices that are not excluded by the filtering
directives in
multipath.conf. It's a lot like lvm.conf. The operating system has no idea what
these devices
will be used for, you must direct it explicitly.
https://help.ubuntu.com/lts/serverguide/multipath-dm-multipath
Public bug reported:
I have multipath-tools installed on my thinkpad to experiment with an
iscsi install we have at work.
Today I tried to mount an SD card inserted into a Transcend TS-RDF8K
reader. No go either from KDE or the command line:
armalota@armalota-thinkpad:~$ sudo mount -t vfat /dev/
It would appear as though the init script is creating the pid with
root:root ownership, irrespective of memcached.conf's contents, yet
still passes the -P during memecached's exec. When the -P option is
added to the config, it results in this error as memcached tries to
create a pid that already ex
Related Debian bug is at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713070
When this is resolved, it should work both apache2.2 and apache2.4.
--
Stig
** Bug watch added: Debian Bug tracker #713070
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713070
--
You received this bug noti
Turns out we have apache2 2.4 in saucy-proposed, but is currently
blocked from being migrated because it breaks other packages. When this
is complete, it should work again.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubunt
Looks like this is because Debian has apache2 2.4.4-6 and Ubuntu is
still on 2.2.22-6ubuntu5. Debian has moved to /etc/apache2/sites-
enabled/puppetmaster.conf, whereas Ubuntu's apache2 still requires
/etc/apache2/sites-enabled/puppetmaster.
--
You received this bug notification because you are a
Public bug reported:
On a fresh Saucy cloud image, "apt-get install puppetmaster-passenger"
fails. Log attached.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: puppetmaster-passenger 3.2.2-1
ProcVersionSignature: User Name 3.9.0-6.14-generic 3.9.6
Uname: Linux 3.9.0-6-generic x86_64
Apport
ubuntu@juju-raring-instance-1:~$ sudo ceph -v
ceph version 0.56.6 (95a0bda7f007a33b0dc7adf4b330778fa1e5d70c)
ubuntu@juju-raring-instance-1:~$ sudo ceph -s
health HEALTH_OK
monmap e2: 3 mons at
{juju-raring-instance-1=10.5.0.52:6789/0,juju-raring-instance-2=10.5.0.39:6789/0,juju-raring-instan
Thanks for reporting this bug.
assignee: utlemming
status: confirmed
importance: medium
** Changed in: lxc (Ubuntu)
Importance: Undecided => Medium
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) => Ben Howard (utlemming
Thanks for reporting this bug.
assignee: utlemming
status: confirmed
importance: low
** Changed in: lxc (Ubuntu)
Importance: Undecided => Low
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) => Ben Howard (utlemming)
--
Public bug reported:
nova-xcp-network places the scripts under /usr/lib/xcp/plugins but
/lib/udev/rules.d/xen-openvswitch-nova.rules calls
/usr/lib/xcp/scripts/ovs_configure_vif_flows.py instead.
# cat /lib/udev/rules.d/xen-openvswitch-nova.rules
SUBSYSTEM=="xen-backend", KERNEL=="vif*",
RUN+="
reproducer script : queue_send.py
** Attachment added: "queue_send.py"
https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1197380/+attachment/3723024/+files/queue_send.py
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Reproducer script : queue_receive.py
** Attachment added: "queue_receive.py"
https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1197380/+attachment/3723025/+files/queue_receive.py
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subsc
Public bug reported:
rabbitmq-server seems to be leaking memory. This has been tested with
Precise, Raring and Saucy
Run the following reproducer (attached to the bug) :
$ while true
do
./queue_send.py
done;./queue_receive.py
a. Actual Results:
Free memory decrease and RSS of the rabbitmq
Public bug reported:
vlotho@pc5:~$ lsb_release -rd
Description:Ubuntu Saucy Salamander (development branch)
Release:13.10
vlotho@pc5:~$ apt-cache policy apache2
apache2:
Installé : 2.2.22-6ubuntu5
Candidat : 2.4.4-6ubuntu2
Table de version :
2.4.4-6ubuntu2 0
500 http:
So this bug doesn't allow me to install openstack devstack.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to iscsitarget in Ubuntu.
https://bugs.launchpad.net/bugs/1072597
Title:
open-iscsi has a bug with ubuntu
To manage notificatio
Public bug reported:
If I run:
sudo lxc-create -t ubuntu-cloud -n wip -- -r saucy -i foobar -s
daily
then the created container still uses a random instance id. grepping for
foobar /etc and /var/lib/cloud gives me nothing.
Expected result:
/var/lib/cloud/data/instance-id should be "foobar"
This bug was fixed in the package iscsitarget - 1.4.20.2-10ubuntu4
---
iscsitarget (1.4.20.2-10ubuntu4) saucy; urgency=low
* d/p/fix-3.10-kernel-match.patch: Fixup patch pattern matching for
>= 3.10 kernels.
* d/p/kernel-3.10-support.patch: Add support for Linux 3.10
(LP:
** Description changed:
lxc 0.9.0-0ubuntu3.3
Running "lxc-create -t ubuntu-cloud -n test -- -i test" creates a Lucid
- container. I expected it to be Raring.
+ container. I expected it to be Raring (when on Raring).
Indeed, on Precise, I believe that you'd get a Precise container.
Public bug reported:
lxc 0.9.0-0ubuntu3.3
Running "lxc-create -t ubuntu-cloud -n test -- -i test" creates a Lucid
container. I expected it to be Raring (when on Raring).
Indeed, on Precise, I believe that you'd get a Precise container.
The culprit appears to be http://bazaar.launchpad.net/~
Public bug reported:
Boot a precise instance with kernel option 'apparmor=0'
Install maas-dhcp
ubuntu@ubuntu:~$ sudo apt-get install -y maas-dhcp
Setting up maas-dhcp (1.2+bzr1373+dfsg-0ubuntu1~12.04.1) ...
Warning: unable to find a suitable fs in /proc/mounts, is it mounted?
Use --subdomainfs to
33 matches
Mail list logo
