Yes, it looks as if the problem is that NM is forgetting the second
nameserver address.
Can you reproduce this malfunction with the Quantal version of network-
manager?
** Package changed: dnsmasq (Ubuntu) = network-manager (Ubuntu)
** Summary changed:
- vpn dns server addresses - host lookups
Reviewed: https://review.openstack.org/14368
Committed:
http://github.com/openstack/nova/commit/86a59376c6d4d2ec5a05c8b63a419d0374e9d9c9
Submitter: Jenkins
Branch:stable/essex
commit 86a59376c6d4d2ec5a05c8b63a419d0374e9d9c9
Author: Michael Still mi...@stillhq.com
Date: Thu Oct 11 15:46:11
Public bug reported:
All of the templates for power and pxe are installed in /usr. They
should be in /etc so that they don't get silently overwritten on
upgrades.
** Affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Tags: qateam
** Tags added: qateam
--
You received
** Branch linked: lp:~allenap/maas/one-tftp-server-per-interface
--
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/1068843
Title:
maas-cluster-controller doesn't have images for
** Also affects: maas (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: maas (Ubuntu Raring)
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Also affects: maas (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: maas (Ubuntu Raring)
Importance: High
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Also affects: maas (Ubuntu Raring)
Importance: Undecided
Status: Confirmed
--
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:
import_pxe_files does not include
** Also affects: maas (Ubuntu)
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.
https://bugs.launchpad.net/bugs/1070775
Title:
The zone name (attached to a cluster
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Also affects: maas (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: maas (Ubuntu Raring)
Importance: Undecided
Status: New
--
You received this bug notification because you are
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Also affects: maas (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: maas (Ubuntu Raring)
Importance: Undecided
Status: New
--
You received this bug notification because you are
** Also affects: maas (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: maas (Ubuntu Raring)
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Also affects: maas (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: maas (Ubuntu Raring)
Importance: Undecided
Status: New
--
You received this bug notification because you are
** Also affects: maas (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: maas (Ubuntu Raring)
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.
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Also affects: maas (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: maas (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: maas (Ubuntu Raring)
Importance:
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Also affects: maas (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: maas (Ubuntu Raring)
Importance: Undecided
Status: New
--
You received this bug notification because you are
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Also affects: maas (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: maas (Ubuntu Raring)
Importance: Undecided
Status: New
--
You received this bug notification because you are
** Also affects: maas (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: maas (Ubuntu Raring)
Importance: High
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Changed in: apache2 (Debian)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1068854
Title:
Support option to disable TLS compression to
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Also affects: maas (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: maas (Ubuntu Raring)
Importance: Undecided
Status: New
--
You received this bug notification because you are
*** This bug is a duplicate of bug 1073238 ***
https://bugs.launchpad.net/bugs/1073238
D'oh, I do believe I tested on a 3.7 kernel, so that would make sense :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
This bug was fixed in the package python-keystoneclient -
1:0.1.3.37-0ubuntu1
---
python-keystoneclient (1:0.1.3.37-0ubuntu1) raring-proposed; urgency=low
[ Adam Gandelman ]
* New upstream release.
[ Adrien Cunin ]
* Typo and cosmetic fixes to package description (LP:
Public bug reported:
Squid3 on Precise does not clean up its PID file, causing logrotate to
spit out an error each night when cron runs it. This is on a server where
we want squid3 installed and ready to go but not running by default.
0 root@rackspace:/etc/mysql#start squid3
squid3
** Also affects: python-tx-tftp (Ubuntu)
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.
https://bugs.launchpad.net/bugs/1068843
Title:
maas-cluster-controller doesn't have
Hi Justin, thanks for the bug. It looks like the dependency between
keystone and python-keystone is explicit in that it requires the same
version, so those should be upgraded together. The python-
keystoneclient dependency is loosely defined, for sure. Can you confirm
that this is the case?
I rebuilt this configuration on a less-restrictive network (identical
DNS/DHCP config, but w/o a firewall), and I was unable to reproduce the
problem. I did observe errors from the DNS server in the problematic
config - they were ipv6 issues. These issues did not correlate w/
failures to use PTR
This bug was fixed in the package python-tx-tftp - 0.1~bzr31-0ubuntu7
---
python-tx-tftp (0.1~bzr31-0ubuntu7) raring; urgency=low
[ Julian Edwards ]
* Add d/p/02-ip-context.patch (LP: #1068843)
-- Andres Rodriguez andres...@ubuntu.com Wed, 31 Oct 2012 10:10:04 +0100
** Branch
That's an Ubuntu packaging issue
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: nova
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
Ok thanks Dann
** Changed in: maas/1.2
Milestone: 12.10-stabilization = None
** Changed in: maas/1.2
Status: Incomplete = Invalid
** Changed in: maas
Status: Incomplete = Invalid
** Changed in: maas (Ubuntu Quantal)
Status: New = Invalid
** Changed in: maas (Ubuntu
Which version are you using?
** Changed in: nova (Ubuntu)
Importance: Undecided = Low
** Changed in: nova (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
This is on Ubuntu 12.04 with Folsom installed using ubuntu-
cloud.archive.canonical.com
--
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/1073510
Title:
Upstart init script executes
Actually, I believe this is fixed as of precise, as the apparmor policy
refuses writes from the container into the /sys/devices/*/uevent files.
(udevadm trigger --add writes 'add' into those files).
** Changed in: lxc (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug
*** This bug is a duplicate of bug 1073238 ***
https://bugs.launchpad.net/bugs/1073238
I'll test that soon too :)
--
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/1071910
Title:
lxc
*** This bug is a duplicate of bug 1073238 ***
https://bugs.launchpad.net/bugs/1073238
:o the memory cgroup dissapeared when I switched to 3.6.3, is it also
gone in 3.7, is that why you asked me to comment out the memory setting?
--
You received this bug notification because you are a
apt (Ubuntu Precise)
running Ubuntu in VM-ware through a proxy and a Secure-Web-Gateway.
To disable the http pipeline when doing a dist-upgrade did the trick for me.
(temporary) sudo apt-get -o Acquire::http::Pipeline-Depth=0 -y dist-upgrade
(permanent) echo 'Acquire::http::Pipeline-Depth 0;'
I'd say the issue lies with Cinder, and may be limited to Ubuntu
packaging.
** Also affects: cinder (Ubuntu)
Importance: Undecided
Status: New
** Project changed: nova = cinder
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
** Bug watch added: Squid Bugzilla #2741
http://bugs.squid-cache.org/show_bug.cgi?id=2741
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
https://bugs.launchpad.net/bugs/16669
Title:
Squid: Compile with
*** This bug is a security vulnerability ***
Public security bug reported:
Apache 2.2 is vulnerable to the CRIME attack. While modern browsers are
not vulnerable to this. older browsers are. And various compliance scans
will check for it.
Apache's bug report --
** Branch linked: lp:~openstack-ubuntu-testing/keystone/raring-grizzly-
proposed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/1073273
Title:
keystone package has incorrect dep
** Branch linked: lp:~openstack-ubuntu-testing/keystone/quantal-folsom-
proposed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/1073273
Title:
keystone package has incorrect dep
Public bug reported:
There are some environments when is a requisite not to boot the server
on install (inside chroots for images creation p.e.). Right now, there
is no way to avoid this.
** Affects: rabbitmq-server (Ubuntu)
Importance: Undecided
Status: New
--
You received this
** Branch linked: lp:~ubuntu-branches/ubuntu/raring/keystone/raring-
proposed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/1073273
Title:
keystone package has incorrect dep on
*** This bug is a duplicate of bug 1073238 ***
https://bugs.launchpad.net/bugs/1073238
Quoting Tim (ice...@gmail.com):
*** This bug is a duplicate of bug 1073238 ***
https://bugs.launchpad.net/bugs/1073238
:o the memory cgroup dissapeared when I switched to 3.6.3, is it also
gone in
*** This bug is a duplicate of bug 1073238 ***
https://bugs.launchpad.net/bugs/1073238
I might try 3.7 later and see if I can get the memory cgroup working
again, but I'm not sure if I really need it.
3.6.3 is working with the memory cgroup disabled, I tested with over 400
iterations, I have
I have been using the folsom-trunk-testing PPA as I thought those
packages would eventually make their way into the Ubuntu Cloud archive.
And yes.. it seems that the keystone, python-keystone, python-
keystoneclient packages all have to be upgraded together as a unit.
--
You received this bug
Debian just released apache2 v2.2.22-12 to address this issue.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1068854
Title:
Support option to disable TLS compression to protect
Public bug reported:
linux-image-3.6.4-030604-generic_3.6.4-030604.201210310737_i386.deb
ProblemType: Package
DistroRelease: Ubuntu 12.10
Package: open-vm-dkms 2012.05.21-724730-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
Uname: Linux 3.5.0-18-generic i686
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1073687
Title:
open-vm-dkms 2012.05.21-724730-0ubuntu2: open-vm-tools kernel module
I have the same problem with quantal (image installed by MAAS)
I've just created a bridge br0 in the interfaces file and now the system does
not boot.
it seems br0 is not going up
if I do a brcrl addbr br0 everything works.
I have not the bonding one, but seems to be the same error.
The
I added a rule in udev to bring up the port directly with brctl addbr
br0 and now everything works.
But I don't know the cause.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vlan in Ubuntu.
https://bugs.launchpad.net/bugs/1003656
Public bug reported:
today all sites require js. also the webpage of a linksys router page
configuration.
So please enable the compilation of javascript support enabled by
default for links and elinks text based browsers
is all.
** Affects: elinks (Ubuntu)
Importance: Undecided
Cinder and nova-api-os-volume use the same port on purpose. You have to
disable the volume api in nova if you want to use cinder.
As mentioned in point 10 here:
http://wiki.openstack.org/MigrateToCinder
You should make sure osapi_volume is ignored in your conf file.
Reviewed: https://review.openstack.org/14790
Committed:
http://github.com/openstack/cinder/commit/524c7fa6dfade6efcabda19b105d58cab8c434e2
Submitter: Jenkins
Branch:master
commit 524c7fa6dfade6efcabda19b105d58cab8c434e2
Author: John Griffith john.griff...@solidfire.com
Date: Wed Oct 24
Fix proposed to branch: stable/folsom
Review: https://review.openstack.org/15157
--
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/1065702
Title:
After folsom upgrade, instances can no
I have tested successfully the proposed update. Thank you!
** Tags removed: verification-needed
** Tags added: verification-done
--
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/1052972
54 matches
Mail list logo
