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
[Expired for qemu-kvm (Ubuntu) because there has been no activity for 60
days.]
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.laun
** Package changed: func (Debian) => debian
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/292955
Title:
[needs-packaging] func
To manage notifications about this bug go to:
https://b
** Changed in: mysql-5.5 (Ubuntu)
Assignee: (unassigned) => e75ice...@aol.com (e75iceman)
--
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/986892
Title:
mysql-server postrm bre
I assume this was a dupe of the other bug, but if the package from
https://launchpad.net/~sssd/+archive/updates doesn't fix it, feel free
to reopen.
** Changed in: nss (Ubuntu)
Status: Confirmed => Invalid
** Changed in: openldap (Ubuntu)
Status: Confirmed => Invalid
** Changed in:
On 29/10/12 21:50, Glenn Coombs wrote:
> The nm-dns-dnsmasq.conf file only shows information relating to the 1st
> server - it seems to have totally ignored the 2nd server:
>
> $ cat /var/run/nm-dns-dnsmasq.conf
> server=/kl.imgtec.org/192.168.15.221
> server=/79.168.192.in-addr.arpa/192.168.15.221
I believe that you might be able to replicate this bug by setting up a
vpn in "Automatic (VPN) addresses only" mode and specifying two DNS
server addresses (one valid and one not). See attached image for
example.
** Attachment added: "snapshot.png"
https://bugs.launchpad.net/ubuntu/+source/dn
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.0.1
search kl.imgtec.org
$ ping glenn.kl.imgtec.org
ping: unknown host glenn.kl.imgtec.org
--
You recei
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu38
---
lxc (0.8.0~rc1-4ubuntu38) quantal-proposed; urgency=low
[ Scott Moser ]
* 0225-ubuntu-cloud-numeric-owner: use --numeric-owner when extracting root
filesystems with tar (LP: #1066084)
[ Serge Hallyn ]
* Remov
The verification of this Stable Release Update has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu38
---
lxc (0.8.0~rc1-4ubuntu38) quantal-proposed; urgency=low
[ Scott Moser ]
* 0225-ubuntu-cloud-numeric-owner: use --numeric-owner when extracting root
filesystems with tar (LP: #1066084)
[ Serge Hallyn ]
* Remov
The verification of this Stable Release Update has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression
Thanks for your suggestion Serge,
I believe I just solved the issue, except for the part I was seeing with
lvremove which appears to have some relation to:
udevd[7497]: timeout: killing 'watershed sh -c '/sbin/lvm vgscan; /sbin/lvm
vgchange -a y'' [11645]
udevd[7497]: 'watershed sh -c '/sbin/lvm
Public bug reported:
Hello,
It seems that configuration fails to read files inside the
/var/lib/maas/ephemeral/tgt.conf.d/ directory.
I was looking around and seems it's a globbing problem of the python
library.
I updated config to include the exact *.conf files and with this change
everything
Public bug reported:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION="Ubuntu 12.04 LTS"
# dpkg -l python-nova
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-require
Anyone know when the fix will be released for 12.04?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to quota in Ubuntu.
https://bugs.launchpad.net/bugs/973663
Title:
quota returns nothing for NFS on 12.04
To manage notifications about
looks good in my testing, too. with bridge-utils 1.5-2ubuntu7 the
previously failing versions of my interfaces file work. our current live
version of the interfaces continues to work, and a variant w/o the "pre-
up" workaround from my initial report works as well. thanks!
--
You received this b
Can you confirm whether commenting out the line:
lxc.cgroup.memory.memsw.limit_in_bytes = 1024M
lets the container start?
--
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
Public bug reported:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION="Ubuntu 12.04 LTS"
Using the following package repo:
# cat /etc/apt/sources.list.d/folsom-source.list
deb
http://ppa.launchpad.net/openstack-ubuntu-testing/folsom-trunk-testing/ubuntu
** No longer affects: cinder
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cinder in Ubuntu.
https://bugs.launchpad.net/bugs/1065511
Title:
cinder incorrectly creating tgt files in /usr/lib/python2.7/dist-
packages/volumes/
To m
** Changed in: tomcat7 (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat6 in Ubuntu.
https://bugs.launchpad.net/bugs/1068405
Title:
catalina.properties use hard references to /var/lib/tomca
** Description changed:
Background:
This is issue occurs during an automated process and occurs with a 1/20
chance per iteration
I have one lxc-container on the machine
It is backed with an lvm2 snapshot
Running on ubuntu 12.10 on ec2 small instance - upgraded from 12.04 fresh
instance
** Changed in: tomcat7 (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat7 in Ubuntu.
https://bugs.launchpad.net/bugs/1031395
Title:
tomcat6 and tomcat7 are not installable side-by-side
To
Public bug reported:
I'm getting a failure in cloud-init on boot
Oct 30 14:34:45 srv-2dg76 [CLOUDINIT] util.py[WARNING]: Running
ssh-authkey-fingerprints ()
failed
Oct 30 14:34:45 srv-2dg76 [CLOUDINIT] util.py[DEBUG]: Running
ssh-authkey-fingerprints ()
failed#012Traceback (most recent call
** Summary changed:
- tomcat7 7.0.30 (or newer) should be backported to precise
+ Please backport tomcat7 7.0.30-0ubuntu1 (main) from raring
** Description changed:
+ Please backport tomcat7 7.0.30-0ubuntu1 (main) from raring to precise.
+
+ Reason for the backport:
+
Oh, one more thing. In 10.10, the disks appeared as /dev/sda#, but from
11.04 and later they're called /dev/xvda#
--
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:
Lo
Blueprint changed by Norvald H. Ryeng:
Whiteboard changed:
Things to discuss:
* What to do about lack of unit tests in recent patch releases of MySQL
* MariaDB and Percona Server in the distro
* Upstream MariaDB and Pecona Server package compatibility w/ distro
* Synchronizing packagi
Yes that's how I did it, ran do-release-upgrade 3 times and rebooted each time.
10.10 -> 11.04 -> 11.10 -> 12.04.1
--
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:
L
Just for clarity, could you describe how you upgraded?
The ami reported here is 'ebs/ubuntu-maverick-10.10-i386-server-20101225'
Meanting to upgrade to 12.04, you would have first had to upgrade to 11.04
then 11.10, then 12.04.
--
You received this bug notification because you are a member o
Blueprint changed by Michelle Surtees-Myers:
Definition Status: Discussion => New
--
Juju GUI
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-juju-gui
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu
** Bug watch added: Debian Bug tracker #685298
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685298
** Also affects: debian via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685298
Importance: Unknown
Status: Unknown
** Package changed: debian => tomcat7 (Debian)
--
You re
** Bug watch added: Debian Bug tracker #691865
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691865
** Also affects: tomcat7 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691865
Importance: Unknown
Status: Unknown
--
You received this bug notification because y
typo in container config, actually using:
lxc.mount = /vms/vm1/fstab
instead of
lxc.mount = /vm1/vm1/fstab
--
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 stop will ha
- Container config:
lxc.utsname = vm1
lxc.tty = 4
lxc.pts = 1024
lxc.rootfs = /vms/vm1/rootfs
lxc.mount = /vm1/vm1/fstab
lxc.network.type = veth
lxc.network.flags = up
lxc.network.name = eth0
lxc.network.link = br0
lxc.network.ipv4 = 192.168.3.2
# Set system resource limitations
lxc.cgroup.cpus
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat7 in Ubuntu.
https://bugs.launchpad.net/bugs/1073159
Title:
tomcat7 7.0.30 (or newer) should be backported to precise
To manage notifications about this bu
Tomcat7 is a java application with isolated dependencies. So there shouldn't be
any real changes needed to adopt the quantal/roaring packages to precise.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat7 in Ubuntu.
https://bugs.l
Public bug reported:
Currently tomcat7 on precise is 7.0.26
quantal an roaring providing 7.0.30
In my opinion it would be good to have the most current tomcat7 version also in
precise-backports.
The goal should be providing the latest tomcat7 stable release also via
backports in the LTS release
** Changed in: maas/1.2
Status: In Progress => Fix Committed
** Changed in: maas
Status: In Progress => Fix Released
--
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
thanks for explanation and workaround. Helped me to solve it on 12.10
--
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 manage
This issue still exists in 12.04.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/676304
Title:
Samba fails with files having colon in file name
To manage notifications about this bug
** Branch linked: lp:~julian-edwards/maas/1.2-backport-boot_images_beat
--
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 pr
** Branch linked: lp:~julian-edwards/maas/boot_images_beat
--
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 provisioning
T
** Changed in: maas
Status: Fix Released => In Progress
--
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 provisionin
** Branch linked: lp:~julian-edwards/maas/1.2-backport-bug-1068843
--
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 provisi
** Changed in: etckeeper (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to etckeeper in Ubuntu.
https://bugs.launchpad.net/bugs/1039627
Title:
etckeeper init with git gives error
To manage not
** Also affects: maas/1.2
Importance: Undecided
Status: New
** Changed in: maas
Milestone: 12.10-stabilization => None
** Changed in: maas/1.2
Milestone: None => 12.10-stabilization
** Changed in: maas/1.2
Status: New => In Progress
** Changed in: maas
Status: In
** Branch linked: lp:~allenap/maas/pass-addresses-to-tftp-backend
--
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 provisio
I have seen a couple more reports of this phenomenon in other fora and I
have invited the parties in question to submit their information here.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.ne
** Changed in: dnsmasq (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/998712
Title:
domain name completion broken when dnsmasq is used
To man
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I am unable to reproduce this problem on a fresh and updated 12.04 cloud
instance. Based on the error message, it looks like this problem came
out of debconf rather than from the exim4 package. Since it seems likel
Blueprint changed by James Page:
Work items changed:
Work items:
Backport argonaut to precise-folsom cloud archive: TODO
Upgrade packaging to bobtail release: TODO
+ MIR for additional dependencies for upstart integration: TODO
Enable upstart configurations in packaging: TODO
Enable XFS
Blueprint changed by James Page:
Definition Status: Discussion => Drafting
--
Ceph Activities for R
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-ceph
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubun
Blueprint changed by James Page:
Work items changed:
Work items:
Backport argonaut to precise-folsom cloud archive: TODO
Upgrade packaging to bobtail release: TODO
Enable upstart configurations in packaging: TODO
Enable XFS recommends in packaging: TODO
Test upgrade paths from 12.10 wi
Blueprint changed by James Page:
Whiteboard changed:
User Stories:
+ Franks want to use Ceph as a back end for Openstack Cinder and Glance
+ and take advantage of the fast copy-on-right cloning of block devices
+ supported in Ceph Bobtail. He is able to deploy this using Juju and MaaS
+ on ha
Blueprint changed by James Page:
Whiteboard changed:
User Stories:
Franks want to use Ceph as a back end for Openstack Cinder and Glance
and take advantage of the fast copy-on-right cloning of block devices
supported in Ceph Bobtail. He is able to deploy this using Juju and MaaS
on ha
And this is not just me:
* http://blog.siansiew.com/2011/10/07/ubuntu-11-04-fsckmotd-bug/
*
http://unix.stackexchange.com/questions/45422/should-i-run-fsck-on-boot-for-an-amazon-ec2-image
More examples can be found on Google.
--
You received this bug notification because you are a member of Ubu
Public bug reported:
After upgrading my Amazon VM to Ubuntu 12.04, every time I log in I get the
following warning:
*** /dev/xvda1 will be checked for errors at next reboot ***
Normally this warning should go away when rebooting with the "reboot"
command -- the FS should be checked at next s
Blueprint changed by James Page:
Whiteboard changed:
User Stories:
Risks:
Test Plans:
+
+ Ceph as a backend for Openstack in the Openstack CI Lab providing per-
+ commit testing of Openstack with Ceph.
+
+ DEP-8 automated testing of Ceph providing gated entry of Ceph packages
+ into
Blueprint changed by James Page:
Whiteboard changed:
User Stories:
Risks:
Test Plans:
Release Note:
+
+ Ubuntu 13.04 include the latest Ceph LTS release, 0.5x.x 'Bobtail'.
+ This release includes support for fast copy-on-write cloning of Ceph
+ RADOS block devices and performance
Public bug reported:
After upgrading my Amazon machine to Ubuntu 12.04, every time I run zsh I get
the following output:
locale_warn:13: * not found
Apparenlty this is caused by the file /etc/profile.d/Z99-cloud-locale-
test.sh in the cloud-init package. zsh always outputs an error when a
gl
Blueprint changed by James Page:
Work items set to:
Work items:
Backport argonaut to precise-folsom cloud archive: TODO
Upgrade packaging to bobtail release: TODO
Enable upstart configurations in packaging: TODO
Enable XFS recommends in packaging: TODO
Test upgrade paths from 12.10 with upstart an
> I would have expected the DNS lookup to fall back to the second server
when it failed to receive a reply from the first server instead of just
giving up.
What is the output of "cat /etc/resolv.conf"?
What happens if you do "ping glenn.kl.imgtec.org"?
--
You received this bug notification beca
62 matches
Mail list logo