This bug was fixed in the package libapache2-mod-perl2 - 2.0.7-1ubuntu1
---
libapache2-mod-perl2 (2.0.7-1ubuntu1) raring; urgency=low
* Resynchronise with Debian (LP: #1071529). Remaining changes:
- Change locales-all to locales.
- Drop dwww from a recommends to a suggests
Last warnings for lintian (2013.1~g1-0ubuntu1_all):
W: nova-common: wrong-name-for-upstream-changelog
usr/share/doc/nova-common/ChangeLog.gz
W: nova-common: non-standard-executable-perm etc/nova/logging.conf 0655 != 0755
W: nova-common: executable-not-elf-or-script etc/nova/logging.conf
W:
Public bug reported:
If you create network interfaces (access ports) in openvswitch, and
configure them in /etc/network/interfaces, failsafe.conf will kick in
and the interfaces get configured after failsafe.conf exits. This adds
two minutes to boot time.
openvswitch config:
ovs-vsctl show
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: tgt (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tgt in Ubuntu.
https://bugs.launchpad.net/bugs/1081495
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu45
---
lxc (0.8.0~rc1-4ubuntu45) raring; urgency=low
[ Stéphane Graber ]
* Allow the container to mount efivars on /sys/firmware/efi/efivars.
efivars is automatically mounted by mountall on UEFI systems, failure to
** Changed in: whoopsie-daisy (Ubuntu)
Status: Fix Committed = Fix Released
--
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/959308
Title:
kvm does not generate a system uuid
This is not fixed yet, the enlistment user data is not fixed.
** Changed in: maas/trunk
Status: Fix Committed = In Progress
** Changed in: maas/trunk
Assignee: Gavin Panella (allenap) = Raphaël Badin (rvb)
** Branch linked: lp:~rvb/maas/enlistment-user-data
--
You received this
Public bug reported:
Rene K. Mueller reports that when an original container does not have an
fstab, lxc-clone still adds a 'lxc.mount = /fstab' line, breaking
container start.
** Affects: lxc (Ubuntu)
Importance: Medium
Status: Triaged
** Changed in: lxc (Ubuntu)
** Changed in: walinuxagent (Ubuntu Precise)
Status: Confirmed = In Progress
** Changed in: walinuxagent (Ubuntu Quantal)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to walinuxagent in
Thank you for your bug report, the issue should be fixed with 1.0 in
raring, the commit fixing it seems to be
http://libvirt.org/git/?p=libvirt.git;a=patch;h=efe6c8021146d046846ead5b5efc9828d97c1ceb
... I'm looking at backporting it to quantal
** Changed in: libvirt (Ubuntu)
Status:
** Branch linked: lp:~louis-bouchard/ubuntu/precise/walinuxagent
/walinuxagent-lp1079897
--
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/1079897
Title:
walinuxagent mangles
While fixing this one, can you also have lxc-clone properly change the
lxc.mount line to point to the clone (if lxc.mount exists for the source).
I thought that was done, but apparently not, I spent half an hour yesterday
trying to figure out why a container was ignoring new fstab entries,
Quoting Stéphane Graber (stgra...@stgraber.org):
While fixing this one, can you also have lxc-clone properly change the
lxc.mount line to point to the clone (if lxc.mount exists for the source).
Are you sure? I looked at the code before filing this and it was doing
the right thing, using
Well, I did a lxc-clone yesterday using a daily build of the staging tree and
it definitely was still pointing at the source.
Now maybe we have some patch in Ubuntu that's not in staging and that fixes
that, or staging recently regressed, not sure...
--
You received this bug notification
** Branch linked: lp:~rvb/maas/fix-origin-adr
--
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/1081701
Title:
The metadata address mentioned in the preseed is wrong.
To manage
** Branch linked: lp:~louis-bouchard/ubuntu/quantal/walinuxagent
/walinuxagent-lp1079897
--
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/1079897
Title:
walinuxagent mangles
potentially relavent information at http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=577925.
** Bug watch added: Debian Bug tracker #577925
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577925
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Actually it's a bit worse than that. The code in the package was not
fixed quite the same way as upstream. Instead of looking for
'lxc.mount[ \t]', it looks for any 'lxc.mount'. If found it removes all
those entries and adds a new fstab entry. The problem is that the
lxc.conf always can have
RE Thomas Hood's #120: That is very interesting, though I admit it is
near the outer limits of my current understanding.
To address the only questions above:
The problem is that the LTSP client, after successfully getting
DHCP assignments, fails to download the pxelinux boot image.
It reports
Blueprint changed by Andres Rodriguez:
Work items changed:
Work items:
[andreserl] SRU django 1.4 GenericIpAddressField to 1.3 for 12.04 (LP:
#1081391): INPROGRESS
[andreserl] SRU django 1.4 prefetch_related to 1.3 for 12.04 (LP: #1081388):
INPROGRESS
[andreserl] SRU django 1.4 upstream
Public bug reported:
[Impact]
As part of the MAAS Next Steps bluepring [1], YUI3 is a required dependency for
MAAS. In Precise, the 'yui3' libraries are being shipped with 'maas' source.
This was done because such libraries weren't in the archives. How that they
are, it is imperative for us to
Blueprint changed by Andres Rodriguez:
Work items changed:
Work items:
[andreserl] SRU django 1.4 GenericIpAddressField to 1.3 for 12.04 (LP:
#1081391): INPROGRESS
[andreserl] SRU django 1.4 prefetch_related to 1.3 for 12.04 (LP: #1081388):
INPROGRESS
[andreserl] SRU django 1.4 upstream
** Description changed:
[Impact]
As part of the MAAS Next Steps bluepring [1], YUI3 is a required dependency
for MAAS. In Precise, the 'yui3' libraries are being shipped with 'maas'
source. This was done because such libraries weren't in the archives. How that
they are, it is imperative
Public bug reported:
[Impact]
As part of the MAAS Next Steps bluepring [1], raphael 2.1.0 is a required
dependency for MAAS. In Precise, the 'raphael' library is being shipped with
'maas' source. This was done because the library version required wasn't in the
archives. However, now that it
** Tags added: needssru
--
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/1084089
Title:
lxc-clone shouldn't add fstab line if it wasn't there originally
To manage notifications about
the LTSP server defers to the router handling DHCP.
OK, I get it.
I don't understand what you said about standalone dnsmasq
conflicting with network-manager's instance of dnsmasq
when /etc/dnsmasq.d/network-manager is removed.
When /etc/dnsmasq.d/network-manager is present, standalone
Thanks for reporting this bug.
As the error message indicated, your hostname is purely numeric and not
valid. Please change your hostname to something not completely numeric,
like 'u10'. Newaliases should then succeed.
Please respond if you need more help to get past this.
** Changed in:
** Changed in: openldap (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1070093
Title:
package slapd (not installed) failed to
** Changed in: clamav (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav in Ubuntu.
https://bugs.launchpad.net/bugs/1072313
Title:
package clamav-milter 0.97.3+dfsg-2.1ubuntu1 failed to
Thanks for submitting this bug report. I can't reproduce it locally.
Could you please do
sudo grep slapd /var/log/syslog syslog.slapd.out
and attach syslog.slapd.out here?
** Changed in: openldap (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you
olutayo - could you please file a new bug for your issue using 'ubuntu-
bug juju' ? This appears to be a different issue. Please make sure to
append a (sanitized) copy of your environments.yaml.
** Changed in: juju (Ubuntu)
Status: New = Invalid
--
You received this bug notification
** Changed in: cloud-init (Ubuntu)
Importance: Undecided = Medium
--
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/1073082
Title:
Login always warns about fsck, but doesn't
I'm not confident enough to mark it Confirmed, but I believe that's
right - an upstart job is needed.
** Changed in: openvswitch (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in
** Changed in: openvswitch (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1084028
Title:
openvswitch based interfaces not started in
Public bug reported:
When using auto.net and mounting multiple remote exports, only one mount works
and autofs steps onto the other mounts.
The problem appears in /proc/mounts (see details in walk-thru below)
HOSTA *
NFS Host (i.e. hosta):
$ uname -a
Linux hosta 2.6.18-274.3.1.el5 #1
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu46
---
lxc (0.8.0~rc1-4ubuntu46) raring; urgency=low
* 0229-lxc-clone-mount-fix: fix wrong handling of lxc.mount entries in
lxc-clone. (LP: #1084089)
* debian/apparmor/abstractions-lxc-container-base: deny read/write
Could you please show the exact configuration files when working and not
working? In which file did the *.conf not work? Certainly the
inclusion of /etc/tgt/conf.d/*.conf from /etc/tgt/targets.conf seems to
be working (just tested under quantal).
** Changed in: tgt (Ubuntu)
Importance:
Thanks for reporting this bug. It looks like racoon is failing to stop.
Could you please do:
sudo service racoon stop
sudo service racoon start
and show the results here?
** Changed in: ipsec-tools (Ubuntu)
Importance: Undecided = Medium
** Changed in: ipsec-tools (Ubuntu)
Status:
Thanks for the explanation of how removal of /etc/dnsmasq.d/network-
manager sets up a conflict between standalone dnsmasq and NM-dnsmasq.
(But also see my surprising observation below.)
Should this conflict be manifesting itself somehow?
Everything seems to be working right now.
Well, I am
Thanks for reporting this bug. Could you please tell us exactly what
steps or commands you were using, and wat you saw for output? Was
postfix already installed? Could you post any results from 'grep
postfix /var/log/syslog /var/log/apt/* /var/log/messages
/var/log/daemon.log ?
** Changed in:
Thanks for reporting this bug. I cannot reproduce this using your
modified vsftpd.conf. Do you get more meaningful error messages if you
simply do
sudo apt-get install --reinstall vsftpd
?
** Changed in: vsftpd (Ubuntu)
Importance: Undecided = Medium
** Changed in: vsftpd (Ubuntu)
** Changed in: lxc (Ubuntu)
Importance: Undecided = Medium
** Changed in: lxc (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/1080681
Title:
Question: Why did everything work on your machine when standalone
dnsmasq wasn't in bind-interfaces mode but /etc/NM/NM.conf contained
dns=dnsmasq?
Hypothesis: Standalone dnsmasq started first; network-manager second. NM
tried to start NM-dnsmasq but this failed because of the address
conflict
As per discussion on #ubuntu-devel, lxc should run MAKEDEV in the
container before setting up its devices.
To do this, teh setup_autodev() function must be split up. We'll first
mount all lxc filesystems (including a fresh /dev), then run MAKEDEV
console in the container, then do the rest of
... except that we can't actually call running-in-container reliably
this early in the boot process; /run is not guaranteed to be mounted (or
seen to be mounted) before /dev.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in
Have talked through this with hallyn in detail.
- we don't want to change MAKEDEV itself to not clobber existing device nodes,
because in other cases this makes recovery from broken /dev less reliable
- we can't side-step this by making /dev not be a mountpoint within the
container because in
Public bug reported:
When attempting to change a quota for one of my customers, with the
command below, I receive an error message instead of the command
succeeding.
What I see:
$ sudo nova-manage project quota --project=
--key=instances --value=15
** Also affects: nova
Importance: Undecided
Status: New
--
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:
'nova-manage project quota' command fails with
I think that I found a workaround that solves part of the problem, editing the
config file and adding the following line:
lxc.network.hwaddr = aa:aa:aa:aa:aa:aa
In that way the ipv4 address is kept through reboots. However it is
still not the same one stated under lxc.network.ipv4.
--
You
** Branch linked: lp:ubuntu/mountall
--
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/1075717
Title:
mounted-dev must not re-create consoles in a container
To manage notifications about
A lxc tree which is working for me to do MAKEDEV console in the
container is at lp:~serge-hallyn/ubuntu/raring/lxc/lxc-makedev.
--
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/1075717
@Enrique,
near as i can tell this turns out to be not an lxc issue (unless we want
the template to be more invasive than it already is).
In Ubuntu it looks like ifup simply is smart enough to not follow
through with dhcp if the nic is already up with an address. In debian,
not.
If you want the
This seems to still be a problem in 12.04. On log out I get
pam_mount(spawn.c:128): error setting uid to 0
pam_mount(mount.c:69): umount messages:
pam_mount(mount.c:73): umount: /home/me/share is not in the fstab (and you are
not root)
pam_mount(mount.c:752): unmount of share failed
This seems
The attachment nova-manage.patch of this bug report has been
identified as being a patch. The ubuntu-reviewers team has been
subscribed to the bug report so that they can review the patch. In the
event that this is in fact not a patch you can resolve this situation by
removing the tag 'patch'
** Branch linked: lp:~julian-edwards/maas/backport-153-packaging.quantal
--
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/1081212
Title:
The address of the API in pserv.conf
** Changed in: mountall (Ubuntu)
Status: Triaged = Fix Committed
--
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/1075717
Title:
mounted-dev must not re-create consoles in a
56 matches
Mail list logo
