seriously? 6 months and this isn't fixed? I just got bit by this after
upgrading and rebooting my LDAP server! Imagine the panic that set in
at first.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libnss-ldap in Ubuntu.
https://bug
In addition, /etc/dhcp/dhclient-exit-hooks.d/ntp is *also* getting in on
the act, doing an ntp restart when it sees ntp service information from
the DHCP server.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bug
Public bug reported:
We're seeing a race between if-up.d/ntpdate and the ntp startup script.
1) if-up.d/ntpdate starts.
2) if-up.d/ntpdate acquires the lock "/var/lock/ntpdate-ifup".
3) if-up.d/ntpdate stops the ntp service [which isn't running anyway].
4) if-up.d/ntpdate starts running ntpdate,
Test case added.
** Description changed:
lightdm precise and gdm precise SRU proposals
-
[Impact]
As was originally stated in the bug summary, ~/.pam_environment is not read
at login if $HOME is encrypted. The lightdm (Precise) and gdm (Precise
Public bug reported:
On Ubuntu 12.04.2 LTS, after an automatic upgrade from openvswitch
1.4.0-1ubuntu1.3 to openvswith 1.4.0-1ubuntu1.4 the brcompat support
does not work any longer.
The brcompat kernel module can be build, installed, and loaded, but
openvswitch-brcompatd will not start with the
** Changed in: server-papercuts
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to xinetd in Ubuntu.
https://bugs.launchpad.net/bugs/43574
Title:
Needs Ubuntu-style init script
To manage not
I mistakingly posted recreate instructions at
https://bugs.launchpad.net/ubuntu/+source/cloud-
init/+bug/1103881/comments/6 . they're not comletely irrelevant there,
but I did intend for that to go here.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which i
To reproduce outside of "cloud", you can basically follow the blog post
that I've got at [1].
Using this user-data to make sure you can login:
#cloud-config-archive
- content: |
#!/bin/sh
echo " $(date -R): user-script run ===" | tee /run/user-script.log
- filename: myjob.conf
content:
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1124384
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Server Team, whi
Thanks, I've fixed the changelog version and distro serie and uploaded
** Changed in: openbsd-inetd (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: openbsd-inetd (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubu
just a bit more info, the cloud-config content above results in writing
/etc/init/part-002.conf a an upstart job.
The debug logs shown here had that file in place (from a previous boot), and
cloud-init overwriting it, then calling (or not calling) reload-configuration.
--
You received this bug
** Attachment added: "dmesg with --debug when 'initctl reload-configuration' is
*not* used"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+attachment/3528636/+files/dmesg-debug-no-reload.txt
--
You received this bug notification because you are a member of Ubuntu
Server T
** Attachment added: "dmesg with --debug when 'initctl reload-configuration' is
used"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+attachment/3528635/+files/dmesg-debug-reload.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, whic
This bug was fixed in the package openvswitch - 1.4.0-1ubuntu1.4
---
openvswitch (1.4.0-1ubuntu1.4) precise-proposed; urgency=low
* Fix compatibility with 3.5 kernel (LP: #1116382):
- d/p/000*.patch: Cherry picked fixes from upstream VCS for kernel 3.5
support, including r
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 openvswitch - 1.4.0-1ubuntu1.4
---
openvswitch (1.4.0-1ubuntu1.4) precise-proposed; urgency=low
* Fix compatibility with 3.5 kernel (LP: #1116382):
- d/p/000*.patch: Cherry picked fixes from upstream VCS for kernel 3.5
support, including r
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
** Attachment added: "dmesg when 'initctl reload-configuration' is *not* used"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1124384/+attachment/3528559/+files/dmesg.no-reload.txt
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: upstart (Ubuntu)
** Attachment added: "dmesg when 'initctl reload-configuration' is used"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1124384/+attachment/3528558/+files/dmesg.reload.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clou
** Description changed:
- Example from failure: https://jenkins.qa.ubuntu.com/job/raring-server-
- ec2/ARCH=amd64,REGION=eu-west-1,STORAGE=ebs,TEST=multi-part-ud,label
- =ubuntu-server-ec2-testing/17/console
+ Under bug 1080841 we made cloud-init invoke 'initctl reload-
+ configuration' after it w
** Description changed:
the overlayfs filesystem does not have inotify support.
As a result, upstart jobs added via config (#upstart-job), will not be
noticed if /etc/init is on a overlayfs filesystem.
cloud-init should probably reload upstart configuration if it adds a job.
This is do
** Description changed:
During a cloud image initialization, the service cloud-final is never
executed if the cloud-config script contains an "upgrade" directive and
upstart is part of the upgraded packages:
TESTCASE:
1. Download a cloud image from http://cloud-images.ubuntu.com/rarin
Awesome, thanks for the info. Will have to try and reproduce this on a
precise host then.
** Also affects: libvirt (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: libvirt (Ubuntu Precise)
Im
** Summary changed:
- cloud-init parses yaml incorrectly
+ reload-configuration can confuse upstart
--
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/1124384
Title:
reload-configur
(ancient distro packaging bug so never valid for QEMU upstream itself;
marking Invalid there)
** Changed in: qemu
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
https://bugs.launchp
I don't see why it really matters if it's not on images; it can go into
-updates pretty much as soon as .2 releases (or possibly slightly before
depending on how my schedule works out).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to op
Closing as invalid for QEMU because it's an Incomplete bug against an
ancient QEMU version.
** Changed in: qemu
Status: Incomplete => Invalid
--
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
@Gunnar: thanks for the work on that issue, for the SRU it would be
useful to have a testcase as well so testers know how to verify if the
fix is working as it should, could you add it to the bug summary?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Just to check that I understand. You have ld.so.conf and/or ld.so.conf.d
entries that point into autofs-mounted directories, and during a package
upgrade, since autofs unmounts, then ldconfig runs by other package
** Patch added: "openssh_lp-952185_raring.patch"
https://bugs.launchpad.net/lightdm/+bug/952185/+attachment/3528167/+files/openssh_lp-952185_raring.patch
** Tags added: patch
** Changed in: openssh (Ubuntu)
Status: Triaged => In Progress
** Changed in: openssh (Ubuntu)
Assignee:
** Branch linked: lp:~gunnarhj/ubuntu/raring/gdm/lp-952185
** Branch linked: lp:~gunnarhj/ubuntu/raring/at/lp-952185
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/952185
Title:
~/
Correction, it is "UseDNS no".
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/300151
Title:
ssh slow during logon, when ENTERING INTERACTIVE SESSION
To manage notifications about t
Restart the dbus service on the ssh server "sudo restart dbus" - that should
help.
If not, try adding "UseDNS=no" to your ssh server's sshd_config file and
restart the service "sudo restart ssh"
If the UseDNS trick works, check your dns server setup.
--
You received this bug notification becaus
** Changed in: python-warlock (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: python-glanceclient (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-warlock in Ubuntu.
h
** Changed in: juju (Ubuntu)
Importance: Undecided => High
--
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/883
Title:
Peer relation listed in relation-ids, but not queryable usin
Jorge - do you still see this issue? I had similar problems and ended
up disabling powernap core management for this reason.
** Changed in: powernap (Ubuntu)
Importance: Undecided => Low
** Changed in: powernap (Ubuntu)
Status: New => Incomplete
--
You received this bug notification
Hi Brian - are you still seeing this issue?
** Changed in: powernap (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to powernap in Ubuntu.
https://bugs.launchpad.net/bugs/850124
Title:
package
** Changed in: python-tx-tftp (Ubuntu)
Importance: Undecided => High
** Changed in: python-tx-tftp (Ubuntu Precise)
Importance: Undecided => High
** Changed in: python-tx-tftp (Ubuntu)
Status: New => Triaged
** Changed in: python-tx-tftp (Ubuntu Precise)
Status: New => Triage
** Changed in: tomcat7 (Ubuntu)
Status: New => Confirmed
** Changed in: tomcat7 (Ubuntu)
Importance: Undecided => Medium
--
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/11235
39 matches
Mail list logo