Yes, I think that Debian bug report #483098 gives the background
information needed to understand what's going on here.
Bind9 should certainly not by default send its (loopback) address to
resolvconf. Bind9 should only send its address to resolvconf if it is
known that named can provide general
Public bug reported:
I have recently upgraded my Openstack installation from the version packaged in
Oneiric to the one packaged in Precise.
After the installation, no floating ip addresses were available to instances.
When running euca-allocate-address returns a NoMoreFloatingIps
exception.
Thomas, is there any chance that you have postfix installed
in the environment where you're seeing the resolvconf job
fail at boot?
Yes, postfix was installed and was causing the resolvconf job to fail at boot.
See https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/933566/comments/6.
I installed postfix 2.8.7-1ubuntu1. It still causes the resolvconf job
to fail at boot.
$ status resolvconf
resolvconf stop/waiting
$ dpkg -l postfix|grep ^ii
ii postfix
2.8.7-1ubuntu1
*** This bug is a duplicate of bug 211631 ***
https://bugs.launchpad.net/bugs/211631
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: samba (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Ok, / is non-sense as it is certainly mounted and also the failing fsck
is fot /mnt. But generally it looks like mountall and cloud-init running
concurrently and anything that opens the device may block a rw access
for the fsck. So any blkid could do that. The window is not very big but
who
@Chris,
Could you please confirm that automount.so is also created? In my tests
with DONTSTRIP=1 locally on my box I noticed that automount.so debug
symbols was not being created while the others were.
Leo
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Public bug reported:
I hit this using the local juju provider on precise with the latest
updates to lxc.
The ubuntu template now automatically generates a hwaddr for the lxc
container when it is created.
However this then get propagated to clones of of this container
resulting in multiple lxc
** Description changed:
I hit this using the local juju provider on precise with the latest
updates to lxc.
The ubuntu template now automatically generates a hwaddr for the lxc
- container when is created.
+ container when it is created.
However this then get propagated to clones of
Not sure If i helps, I had sssd working in 12.04 with Alpha 1...never
thought to look at the package version for openldap, but what ever
version was included with Alpha 1 was ok. If that helps
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Blueprint changed by Serge Hallyn:
Whiteboard changed:
Status: Started
NOTE: (jdstrand) jjohansen's work items are being tracked as part ot
security-p-apparmor-containers and I added a dependency of this bp to
that one
Work Items:
[serge-hallyn] LXC init script to create default
This appears to be working on a MB Pro 8,2. Install lm-sensors, run
sensors-detect and follow the bouncing ball.
** Changed in: linux (Ubuntu Precise)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Blueprint changed by Chuck Short:
Whiteboard changed:
Etherpad:
edit: http://pad.ubuntu.com/uds-p-servercloud-p-openstack
time slider:
http://pad.ubuntu.com/ep/pad/view/uds-p-servercloud-p-openstack/latest
- add some mechanism to promote ubuntu images, options:
- populate
This bug was fixed in the package nova -
2012.1~e4~20120217.12709-0ubuntu1
---
nova (2012.1~e4~20120217.12709-0ubuntu1) precise; urgency=low
[ Dave Walker (Daviey) ]
* New upstream snapshot
* debian/patches/temp_fix_linux_net.patch:
- Dropped, applied upstream. LP: #929127
This bug was fixed in the package nova -
2012.1~e4~20120217.12709-0ubuntu1
---
nova (2012.1~e4~20120217.12709-0ubuntu1) precise; urgency=low
[ Dave Walker (Daviey) ]
* New upstream snapshot
* debian/patches/temp_fix_linux_net.patch:
- Dropped, applied upstream. LP: #929127
** Branch linked: lp:ubuntu/nova
--
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/929127
Title:
linux_net.ensure_metadata_ip() fails on precise
To manage notifications about this bug
You have been subscribed to a public bug:
I have a Ubuntu 10.4.2 server, updated to the latest binaries.
I have attempted to install bacula using apt-get install bacula. The
process seems to go well until the various dialogues to set up the MySQL
db connection. After entering the password, the
I have been able to reproduce this in 12.04 with bacula-server
5.2.5-0ubuntu3.
** Changed in: bacula
Status: New = Confirmed
** Project changed: bacula = bacula (Ubuntu)
** Changed in: bacula (Ubuntu)
Importance: Undecided = Medium
** Summary changed:
- Bacula installation fails at
This is fix-committed in revno 518 and 517 [1,2]
--
[1] http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/revision/518
[2] http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/revision/517
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Not quite fixed then, but I've reproduced this and see what's going
wrong.
** Changed in: postfix (Ubuntu)
Status: Fix Released = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
This bug was fixed in the package postfix - 2.8.7-1ubuntu2
---
postfix (2.8.7-1ubuntu2) precise; urgency=low
* debian/init.d: if postmulti fails (which for some reason it does when
the rootfs is read-only in early boot!), the init script 'status'
command returns zero
This is no longer applicable to the new codebase in keystone master.
** Changed in: keystone
Status: In Progress = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
** Changed in: linux (Ubuntu Precise)
Importance: Undecided = Medium
--
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/925028
Title:
apparmor breaks lxc-start-ephemeral
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
--
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/925024
Title:
apparmor makes it impossible to install postgresql-common
This bug was fixed in the package udev - 175-0ubuntu5
---
udev (175-0ubuntu5) precise; urgency=low
[ David Henningsson ]
* Remove jack-detection.patch: Now that PulseAudio uses the new jack
detection interface, we can remove this patch.
[ Stéphane Graber ]
*
** Changed in: linux (Ubuntu)
Status: Incomplete = 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/925024
Title:
apparmor makes it impossible to install
** Changed in: lxc (Ubuntu)
Importance: Undecided = Medium
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Public bug reported:
$ nova boot --image=$img_id --flavor=1 --meta=a=b=c myname
ERROR: dictionary update sequence element #0 has length 3; 2 is required
Simple fix is in novaclient/v1_1/shell.py '_boot' to do:
-meta = dict(v.split('=') for v in args.meta)
+meta = dict(v.split('=',1) for
*** This bug is a duplicate of bug 833073 ***
https://bugs.launchpad.net/bugs/833073
** This bug has been marked a duplicate of bug 833073
oneiric gdm picker list contains system user, rabbitmq
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: rabbitmq-server (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rabbitmq-server in Ubuntu.
** Changed in: bind9 (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/933723
Title:
resolvconf creating bogus resolv.conf file
To manage
Public bug reported:
ii nova-api 2012.1~e4~20120210.12574-0ubuntu1 OpenStack Compute - API
frontend
# curl -s http://169.254.169.254/2008-02-01/meta-data/ami-launch-index
1
This should be zero indexed like on amazon:
# curl -s http://169.254.169.254/2008-02-01/meta-data/ami-launch-index
0
**
** Changed in: bind9 (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/681536
Title:
/usr/share/bind9/bind9-default.md5sum should be in
** Changed in: cloud-init (Ubuntu)
Status: Triaged = Fix Released
--
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/892554
Title:
SSH keys summary does not report ECDSA key
This sounds like 933723 will fix it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/437783
Title:
bind9 failed to start : resolvconf: Error: /etc/resolv.conf must be a
symlink
To
** Summary changed:
- rndc-confgen does nothing
+ rndc-confgen is silent during key genration
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/697609
Title:
rndc-confgen is silent
** 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/934540
Title:
package bacula-common-pgsql 5.2.3-0ubuntu2 failed to install/upgrade:
trying to
--
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/934540
Title:
package bacula-common-pgsql 5.2.3-0ubuntu2 failed to install/upgrade:
trying to overwrite
** Changed in: bind9 (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/929563
Title:
apparmor profile does not include local overrides
Public bug reported:
647 upgrades to the 64 12.04 Ubuntu server with the Unity desktop
interface
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: bacula-common-pgsql 5.2.3-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-11.19-generic 3.2.1
Uname: Linux 3.2.0-11-generic x86_64
ApportVersion:
This was fixed in trunk revision 479 and included in current 0.6.3~ bzr
snapshots in 12.04.
** Changed in: cloud-init (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
Blueprint changed by Daniel Lezcano:
Whiteboard changed:
Status: Started
NOTE: (jdstrand) jjohansen's work items are being tracked as part ot
security-p-apparmor-containers and I added a dependency of this bp to
that one
Work Items:
[serge-hallyn] LXC init script to create
The next upload of bind9 will default to not enabling resolvconf, since
there is no way for it to guarantee that it can resolve addresses and is
not behind some egress-filtering firewall.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Note that Ubuntu, like many linux distributions, backports security
fixes rather than upgrading to new versions of software to attempt to
prevent the introduction of regressions and changes in behavior in
released versions of software.
CVE-2010-3069 was addressed in
Also, you can check the status yourself of the CVEs we are aware of at
the Ubuntu Security cve tracker: http://people.canonical.com/~ubuntu-
security/cve/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
@Brad,
I would consider this a high priority bug. This pretty much means that
containers cannot be protected by apparmor, because we can't predict
when they might be - for no apparent reason - unable to access some file
which they should be able to access.
--
You received this bug notification
This bug was fixed in the package lxc - 0.7.5-3ubuntu28
---
lxc (0.7.5-3ubuntu28) precise; urgency=low
* 0045-fix-other-templates: lots of template fixes. Make sshd, debian,
fedoray, and busybox templates actually work. Fix inconsistent --auth_key
vs --auth-key usage in
Blueprint changed by Serge Hallyn:
Whiteboard changed:
Status: Started
NOTE: (jdstrand) jjohansen's work items are being tracked as part ot
security-p-apparmor-containers and I added a dependency of this bp to
that one
Work Items:
[serge-hallyn] LXC init script to create default
Blueprint changed by Serge Hallyn:
Whiteboard changed:
Status: Started
NOTE: (jdstrand) jjohansen's work items are being tracked as part ot
security-p-apparmor-containers and I added a dependency of this bp to
that one
Work Items:
[serge-hallyn] LXC init script to create default
[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.
Public bug reported:
MySQL 5.5 installation thru deb download failed. Purged 5.5 and
installed 5.1 using apt-get install. This attampt failed.
I recovered by purging 5.1 and reinstalling. MySQL works now but may be
this report will help debug something.
TT
ProblemType: Package
DistroRelease:
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in Ubuntu.
https://bugs.launchpad.net/bugs/934763
Title:
package mysql-client-5.1 5.1.54-1ubuntu4 failed to install/upgrade:
trying to overwrite '/usr/bin/mysqlaccess',
53 matches
Mail list logo
