In Ubuntu 12.10 this issue is as prominent as ever.
On resume from RAM or after boot, dnsmasq requires about 5 minutes to
resolve names correctly.
Workaround: For ssh I use IP addresses
Thunderbird requires a 5 Minute waiting period after resume
Evolution requires two or three attempts to start,
Hello, Is anyone working on this bug? Since it's been about one more
month without update?
--
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/1070190
Title:
maas-enlist does not show on
You may be right that developing a new nm-dns module would be easier
than trying to enhance the existing dns module to support nonstandard
ports.
But the more immediately relevant comparison is the comparison between
the current solution and any solution involving a new or an enhanced NSS
module.
Public bug reported:
I can't add anything to the summary
ProblemType: Package
DistroRelease: Ubuntu 12.10
Package: php5-common 5.4.6-1ubuntu1.1
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu6
Blueprint changed by James Page:
Work items changed:
Work items:
Backport argonaut to precise-folsom cloud archive: DONE
+ Upstream support for XFS in ceph-disk-*: DONE
+ MIR for additional dependencies for upstart integration: INPROGRESS
+ Write dep8 tests for ceph and get automated:
Blueprint changed by James Page:
Work items changed:
Work items:
Backport argonaut to precise-folsom cloud archive: DONE
Upgrade packaging to bobtail release: TODO
- MIR for additional dependencies for upstart integration: TODO
+ MIR for additional dependencies for upstart integration:
Blueprint changed by James Page:
Work items changed:
Work items:
Backport argonaut to precise-folsom cloud archive: DONE
Upstream support for XFS in ceph-disk-*: DONE
- MIR for additional dependencies for upstart integration: INPROGRESS
+ MIR for additional dependencies for upstart
** Branch linked: lp:ubuntu/cloud-init
--
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/1080985
Title:
'noblock' setting for resize_rootfs is broken
To manage notifications about
** Branch linked: lp:ubuntu/cloud-init
--
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/1079002
Title:
Sudoers writing broken when string
To manage notifications about this bug
** Branch linked: lp:ubuntu/cloud-init
--
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/1077020
Title:
cloud-init ca-certs leaves a blank line in /etc/ca-certificates.conf
To
Not a bug in php5, your dpkg database looks broken.
** Package changed: php5 (Ubuntu) = dpkg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1086328
Title:
package
Blueprint changed by James Page:
Work items changed:
Work items:
Backport argonaut to precise-folsom cloud archive: DONE
Upstream support for XFS in ceph-disk-*: DONE
MIR for additional dependencies for upstart integration: DONE
Write dep8 tests for ceph and get automated: INPROGRESS
Blueprint changed by James Page:
Work items changed:
Work items:
Backport argonaut to precise-folsom cloud archive: DONE
Upstream support for XFS in ceph-disk-*: DONE
MIR for additional dependencies for upstart integration: DONE
Write dep8 tests for ceph and get automated: INPROGRESS
Blueprint changed by Chuck Short:
Work items changed:
Work items:
Release and package nova, glance, keystone, cinder, swift, horizon, quantum,
and ceilometer for main: INPROGRESS
MIR dependencies that need to be done for ceilometer: TODO
SSL support openstack endpoints: TODO
Apparmor
(Note that if lxc.network.name is not specified (or is the same as
lxc.network.link) then this doesn't happen, which is a workaround for
this)
There is currently no code in lxc renaming the nics at container
shutdown. That needs to be added.
** Changed in: lxc (Ubuntu)
Status: New =
ok
** Changed in: cloud-init (Ubuntu Precise)
Status: Triaged = Fix Released
** Changed in: cloud-init (Ubuntu Precise)
Assignee: (unassigned) = todaioan (alan-ar06)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bind9 (Ubuntu)
Status: New = Confirmed
--
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/604283
** Package changed: ifupdown (Debian) = bind9 (Ubuntu)
** Changed in: bind9 (Ubuntu)
Importance: Unknown = Undecided
** Changed in: bind9 (Ubuntu)
Remote watch: Debian Bug tracker #617268 = None
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I assign this back to bind9 only because, so far as I can tell, I
inadvertently de-assigned it from bind9 a while back. I don't mean to
imply that I think that there is a problem with bind9.
I'll go further. Now that the NetworkManager-controlled dnsmasq process
listens at 127.0.1.1, it's an
** Changed in: dovecot (Ubuntu Raring)
Assignee: (unassigned) = James Page (james-page)
--
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/671065
Title:
deliver broken because
Public bug reported:
In asterisk 1.8, calls to queues with a 'ringall' strategy will kill
the Dial() of all non-answering agents as soon as another agent
answers. This kill doesn't respect the 'g' option given to Dial(),
i.e. control is never returned to the dialplan. This appears to be a
** Also affects: bind9 (Ubuntu Precise)
Importance: Undecided
Status: New
--
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/1085593
Title:
bind 9.8.1-P1 crashes with an
** Summary changed:
- lxc-stop on precise: 'phys' interface does not come back after lxc-stop
+ 'phys' interface does not come back after lxc-stop
** Description changed:
-
Running 'lxc 0.7.5-3ubuntu65' on 12.04.1 LTS [Precise Pangolin]
Created a container with lxc.network.type=phys. I
Why did you mark this fix-released in precise? The upload went to
raring to fix it.
** Changed in: cloud-init (Ubuntu Precise)
Status: Fix Released = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in
The fix is pushed to the github staging tree. It will be rolled into
raring when 0.9.0 is released and merged.
** Changed in: lxc (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
Blueprint changed by James Page:
Work items changed:
Work items:
Backport argonaut to precise-folsom cloud archive: DONE
Upstream support for XFS in ceph-disk-*: DONE
MIR for additional dependencies for upstart integration: DONE
- Write dep8 tests for ceph and get automated: INPROGRESS
+
** Description changed:
This is a meta-bug used for tracking progress of the 2012.2.1 Folsom
stable update to Nova, Horizon, Keystone, Glance, Cinder and Quantum.
+
+ cinder (2012.2.1-0ubuntu1) quantal-proposed; urgency=low
+ .
+* Ubuntu updates:
+ - Cinder should suggest
man page is generated in packaging - not part of the upstream keystone
repo
** Also affects: keystone (Ubuntu)
Importance: Undecided
Status: New
** Changed in: keystone
Status: Triaged = Invalid
** Changed in: keystone
Assignee: Adam Gandelman (gandelman-a) = (unassigned)
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) = Jamie Strandboge (jdstrand)
--
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/509647
Title:
[MIR] lxc
To manage notifications
Thanks, Joseph. Looks like there are a bunch of stale and unneeded man
pages leftover from the pre-redux days.
** Summary changed:
- Spelling errors reported on IRC
+ man pages installed with keystone are outdated
** Changed in: keystone (Ubuntu)
Status: New = Confirmed
** Changed in:
This has been fixed in the upstream staging tree. The fix should be
merged into raring as soon as 0.9.0 is released and merged.
** Changed in: lxc (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I get different error messages, butthe same result (in raring).
** Changed in: lxc (Ubuntu)
Importance: Undecided = Low
** 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
Blueprint changed by Antonio Rosales:
Whiteboard changed:
Discussion:
*Bug submission on charm failure.
*Define a process around how charm maintainers respond to test failures and
subsequent bugs. Can a user run a manual test and submit the test back to the
bug report to update testing
Public bug reported:
mbp@faith% sudo etckeeper --help
No manual entry for etceeper
Usage: etckeeper command [-d directory]
mbp@faith% dpkg -l etckeeper
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/
Specifically
/usr/bin/etckeeper: man etceeper || echo Usage: etckeeper command
[-d directory] 2
--
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/1086568
Title:
`etckeeper
** Tags added: ec2
--
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/1057196
Title:
IP Protocol for security group should be returned in lower case to be
compliant with the ec2 api
To
Probably valid for the ubuntu distro, but not for Horizon since this
code doesn't exist in the main project.
** Changed in: horizon
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
but this seems to be fixed in head:
http://git.kitenet.net/?p=etckeeper.git;a=blob;f=etckeeper;h=fad1f20a662d12ebb8637b7f1a1c2e7297c4b665;hb=refs/heads/master
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to etckeeper in Ubuntu.
Public bug reported:
The tomcat-dbcp.jar does not contains dbcp packages but jdbc instead.
If you need theses classes java will launch an exception. As a tomcat-dbcp.jar
is present you will be puzzled.
Theses classes are used by the web application to communicated with db. They
are used by
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 python-tx-tftp - 0.1~bzr31-0ubuntu6.1
---
python-tx-tftp (0.1~bzr31-0ubuntu6.1) quantal-proposed; urgency=low
[ Julian Edwards ]
* Add d/p/02-ip-context.patch: Allow the backend to know from what
address the request came from. (LP: #1068843)
** Branch linked: lp:~openstack-ubuntu-testing/horizon/precise-folsom
--
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/1085255
Title:
Meta bug for tracking Openstack 2012.2.1 Stable
** Branch linked: lp:~openstack-ubuntu-testing/horizon/precise-folsom
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/1076216
Title:
Edit image popup public checkbox not pulling in
Confirmed in 0.61ubuntu2.
** Changed in: etckeeper (Ubuntu)
Status: New = Triaged
** Changed in: etckeeper (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to etckeeper in Ubuntu.
Public bug reported:
From my testing, it seems if you have a multipart user-data file that
contains both a boothook and a shell script, the latter will not run. I
have been testing with all sorts of user-data files and only in this
setup (a boothook AND a script) do I see the shell script not run
To my own surprise I haven't seen any complaints related to the switch
from 127.0.0.1 to 127.0.1.1, even though I have been following AskUbuntu
and ubuntuforums.
It's possible that a large portion of Ubuntu users that are using dnsmasq as a
DNS server, only use LTS releases, so complains might
Yes, we should do this.
** Changed in: juju-core
Milestone: None = 1.9.4
** Changed in: juju-core
Assignee: (unassigned) = Dave Cheney (dave-cheney)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
** Changed in: juju-core
Milestone: None = 2.0
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1078213
Title:
juju-machine-agent.log/logs are not logrotated
To manage
Btw please don't backport the current solution to Precise
In comment #110 MTL said that backporting the fix to Precise *is*
planned.
Quantal includes dnsmasq 2.63 which has the new bind-dynamic option.
In bind-dynamic mode dnsmasq works as it does in bind-interfaces mode
but also updates its
** Changed in: apache2 (Ubuntu)
Status: In Progress = Triaged
** Changed in: apache2 (Ubuntu)
Assignee: Chuck Short (zulcss) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
I wrote in comment #131:
What benefits would the nm-dns module or the enhanced
dns module give us relative to what we have now? One is:
the ability to run nm-dnsmasq on another port, freeing up
port 53 for BIND named listening on ALL:53. What else?
I just installed bind9 and was surprised to
51 matches
Mail list logo
