Problem solved by changing BIND configuration according to this article:
http://www.daemonforums.org/showthread.php?t=4471
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
I confirm the version in proposed fix the issue:
* before installing proposed version, on fully updated precises : I still
reproduce the bug
* after installing slapd from proposed : I can't reproduce the bug.
Also on this machine, LDAP is used for local authentication, which still
work after
What happens if I trun on the cleanup and I have instances residing on a
glusterfs. Briefly reading the code (Ubuntu essex release) the image
does not get marked in use and will be removed. Is that correct?
If so, would this be configurable let's say with a
instances_path_is_shared flag?
--
You
Seems to be still present in Ubuntu 12.04. At least, I get the same
symptoms.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/398366
Title:
Certs generated with TinyCA2 and openssl
SRU verification for Precise:
I have reproduced the problem with krb5 1.10+dfsg~beta1-2ubuntu0.1 in
precise-updates and have verified that the version of krb5
1.10+dfsg~beta1-2ubuntu0.2 in -proposed fixes the issue.
Marking as verification-done
** Description changed:
I was trying to
** Also affects: vlan (Ubuntu)
Importance: Undecided
Status: New
--
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/353835
Title:
NetworkManager lacks 802.1Q/VLAN tagging
I found this activity upstream:
https://mail.gnome.org/archives/networkmanager-
list/2011-October/msg00209.html
which seems to be the basis for the claim that VLAN support has been
added to NM. But this is only support for VLANs in RedHat and ilk.
--
You received this bug notification
What helped us was simply rebooting the node using PXE (the node should be in
allocated state). The node in ready state ends up shut down. So basically what
juju does is sending a wake-on-lan signal to start it. If you (like us) powered
the node up in ready state, you end up with this
** Summary changed:
- Pleas add 802.1Q/VLAN tagging support to NetworkManager
+ Please add 802.1Q/VLAN tagging support to NetworkManager
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vlan in Ubuntu.
** Changed in: postfix (Ubuntu)
Assignee: (unassigned) = Scott Kitterman (kitterman)
** Also affects: postfix (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: postfix (Ubuntu Precise)
Status: New = Triaged
** Changed in: postfix (Ubuntu Precise)
2.9.3 is in precise-updates.
** Changed in: postfix (Ubuntu Precise)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/991754
Title:
Add
fixed in trunk revno 609.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New = Fix Committed
** Changed in: cloud-init
Assignee: (unassigned) = Scott Moser (smoser)
--
You received this bug notification because you are a
** Branch linked: lp: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/1018554
Title:
write timestamp to console on halt/reboot/shutdown
To manage notifications about
You have been subscribed to a public bug:
It's common for people to run:
euca-add-keypair $USERNAME ${USERNAME}.key
which works fine if your keypar is not already added. If it is added,
the .key file is overwritten with a message saying the keypair is
already added.
If we could have the
Hi Clint, Same thing this morning.
Also, if I go here:
https://launchpad.net/ubuntu/+source/openvswitch/1.4.0-1ubuntu1.1/+build/3682163
I don't see a package built for openvswitch-datapath-dkms.
Thanks,
Aaron
--
You received this bug notification because you are a member of Ubuntu
Server
I've marked this Wont' fix if you have a suggestion of a better way to
do this, you could open that upstream with euca2ools.
However, thank you for taking the time to open a bug in ubuntu, I hope
I've explained the response well.
--
You received this bug notification because you are a member of
I don't use mysql maps, but from a packaging perspective this looks
reasonably easy to fix. The tricky part (for me) will be testing it.
If you would send me a copy of your /etc/postfix/mysql-
virtual_aliases.cf (in private if you prefer and with the database
password changed - I don't need DB
I cannot send you the one we use on the server. However, this one should
work:
hosts = www.ubuntu.com
user = testuser
password = testpassword
dbname = testdb
query = SELECT toAddress FROM mailgw_aliases WHERE fromAddress='%s'
If you get the following error then the problem still persists:
@Aaron,
I believe there is a PPC build failure that is blocking it. Do the failures
in the build log look like anything obvious to you?
https://launchpadlibrarian.net/75199/buildlog_ubuntu-precise-
powerpc.openvswitch_1.4.0-1ubuntu1.1_FAILEDTOBUILD.txt.gz
--
You received this bug
You have been subscribed to a public bug:
я не знаю
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: libldap-2.4-2 2.4.28-1.1ubuntu4 [modified:
usr/share/doc/libldap-2.4-2/changelog.Debian.gz]
ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
Uname: Linux 3.2.0-27-generic x86_64
Perfect. I'll try that.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1023550
Title:
Postfix missing libresolv in chroot jail
To manage notifications about this bug go to:
** Package changed: ubuntu = openldap (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1029415
Title:
package libldap-2.4-2 2.4.28-1.1ubuntu4 [modified:
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/974046
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Server Team,
I believe there is a PPC build failure that is blocking it. Do the
failures in the build log look like anything obvious to you?
It's obviously the bug fixed here:
http://openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=commitdiff;h=f79982ba930364f2d3935196dc13b422ba711ef2
I guess we get to
Since this is associated with a manditory test, and is key functionality
not working for A3, upping the importance on this bug.
** Changed in: maas (Ubuntu)
Importance: Medium = High
** Also affects: maas (Ubuntu Quantal)
Importance: High
Assignee: Andres Rodriguez (andreserl)
On Thursday, July 26, 2012 04:18:27 PM you wrote:
I guess we get to re-apply every bug fix from branch-1.4 one at a time
as you guys notice them. Sigh.
The criteria for post-release fixes can be found here:
https://wiki.ubuntu.com/StableReleaseUpdates#When
I think any fixes you have that fit
This bug was fixed in the package krb5 - 1.10+dfsg~beta1-2ubuntu0.2
---
krb5 (1.10+dfsg~beta1-2ubuntu0.2) precise-proposed; urgency=low
* Re-introduce libkrb53 as a transitional package to libkrb5-3.
Also revert the Conflicts against libkrb53 to the old versioned
I'm getting something that sounds a lot like this bug in 12.04 LTS Server - I
have a dual interface home server with 2 nics. ssh, xinetd, and
isc-dhcp-server all fail to work correctly on boot and need to be restarted.
All 3 also have custom configurations for binding to one nic or the other.
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 tomcat7 - 7.0.26-1ubuntu1.1
---
tomcat7 (7.0.26-1ubuntu1.1) precise-proposed; urgency=low
* Fix handling of JNDI lookups using javax.naming.Name (LP: #1012794):
- d/patches/0012-lp-1012794-fix-jndi-lookup.patch: Cherry picked patch
from
** Changed in: lxc (Ubuntu Precise)
Importance: Undecided = High
** Changed in: lxc (Ubuntu Precise)
Status: Fix Released = Triaged
** Changed in: lxc (Ubuntu Precise)
Assignee: (unassigned) = Stéphane Graber (stgraber)
** Changed in: lxc (Ubuntu Quantal)
Assignee: Serge
No worries James, thanks for the quick turnaround!
On Thu, Jul 26, 2012 at 1:12 PM, James Page james.p...@ubuntu.com wrote:
John - thanks for your help on the test case for this SRU - very much
appreciated.
--
You received this bug notification because you are subscribed to the bug
report.
** Changed in: sqlalchemy (Ubuntu Quantal)
Status: In Progress = Fix Released
** Changed in: sqlalchemy (Ubuntu Precise)
Importance: Undecided = High
** Changed in: sqlalchemy (Ubuntu Precise)
Status: Fix Released = In Progress
--
You received this bug notification because you
Any idea why this happened? The previous package Adam gave me fixed this
bug and built correctly.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1021530
Title:
[SRU] update to
SRU team: Please wait for matching lxc upload before accepting into
-proposed or moving to -updates or creating container will fail because
of the broken check in lxc-ubuntu and lxc-ubuntu-cloud.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Description changed:
[rational]
Current initscripts doesn't deal properly with chroots, bind-mounting
/run/shm to /dev/shm instead of making the later a symlink to the former.
LXC has been carrying a workaround for that, sadly the workaround stopped
working late in the 12.04 cycle,
Hello Gary, or anyone else affected,
Accepted sysvinit into precise-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/sysvinit/2.88dsf-13.10ubuntu11.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Gary, or anyone else affected,
Accepted lxc into precise-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/lxc/0.7.5-3ubuntu61 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Branch linked: lp:ubuntu/precise-proposed/lxc
--
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/974584
Title:
Semaphores cannot be created in lxc container
To manage notifications
** Branch linked: lp:ubuntu/precise-proposed/sysvinit
--
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/974584
Title:
Semaphores cannot be created in lxc container
To manage
Aaron, the package posted earlier was built on a PPA, which only targets
i386 and amd64. I've just tested Ben's patch against PPC and proposed a
new upload to precise-proposed.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Tags added: rls-q-incoming
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/1014347
Title:
NUT License prevents distribution of SSL-enabled builds
To manage notifications about this
No, it's supported in NM regardless of the distro used; it's just not
easy to configure; depends on the proper use of the config files.
Closing as Fix Released.
To configure it you'll need to create a new connection manually in
/etc/NetworkManager/system-connections; something like a file
The available parameters for the [vlan] block are defined in source:
http://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/libnm-util/nm-setting-vlan.c#n608
However, the actual names to use (as key=) for the parameters are the
NM_SETTING_VLAN_* constants; which are defined here:
OK, but where is this documented other than here? Can we reopen this as
a wish for additional documentation of some sort?
--
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/353835
Title:
** Also affects: cobbler (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: cobbler (Ubuntu Quantal)
Importance: Medium
Assignee: Andres Rodriguez (andreserl)
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server
https://launchpad.net/ubuntu/+source/cobbler/2.2.2-0ubuntu35
** Changed in: cobbler (Ubuntu Quantal)
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cobbler in Ubuntu.
+1 for support it
Linux is nearly totally safe if all sofware source are authencicated
but in the practical case, users will bypass its check very easily by following
others *recipes*
For example, PPAs are DANGEROUS.
--
You received this bug notification because you are a member of Ubuntu
Thanks to everybody. That helped a lot.
Now, is there any chance to get the VLAN connection up as soon as a
cable is connected? This works fine for 802-3-ethernet connections, but
apparently not for VLAN connections, right?
Unfortunately, nm-applet does not even show the connection at all. I
I think you can do this already with the clamfs package, although I
didn't try it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav in Ubuntu.
https://bugs.launchpad.net/bugs/565036
Title:
For a real-time protection in clamav
That worked. It turns out to be a one liner to fix it in the init
thanks to the way Lamont set it up. I've uploaded a test package to my
PPA - https://launchpad.net/~kitterman/+archive/ppa for precise. I just
now uploaded, so it'll be a bit before the packages are built. If you
can verify this
** Description changed:
+ [IMPACT]
+
+ By hostname map lookups in the chroot fail. This requires users to
+ either unchroot their postfix, which is a less secure configuration,
+ manually create symlinks, or refer to remote map locations by IP address
+ (which is not a very maintainable
** Branch linked: lp:ubuntu/quantal-proposed/maas
--
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/974046
Title:
running just the command maas causes an error
To manage notifications
Thanks Adam, will you let me know when it should be on precise-proposed
so I can give it a quick test? Doesn't seem to be there yet..
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
Public bug reported:
On 12.04, python-greenlet-dbg apparently does not include the debug
symbols:
ubuntu@server-4821~$ sudo apt-get -y install python2.7-dbg python-greenlet
python-greenlet-dbg
ubuntu@server-481:~$ python2.7 -c 'import greenlet'
ubuntu@server-481:~$ python2.7-dbg -c 'import
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu21
---
lxc (0.8.0~rc1-4ubuntu21) quantal; urgency=low
[ Stéphane Graber ]
* Fix lxc-ubuntu and lxc-ubuntu-cloud to fix the /dev/shm workaround to only
trigger when /dev/shm is not a symlink. (LP: #974584)
[ Serge
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu21
---
lxc (0.8.0~rc1-4ubuntu21) quantal; urgency=low
[ Stéphane Graber ]
* Fix lxc-ubuntu and lxc-ubuntu-cloud to fix the /dev/shm workaround to only
trigger when /dev/shm is not a symlink. (LP: #974584)
[ Serge
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu21
---
lxc (0.8.0~rc1-4ubuntu21) quantal; urgency=low
[ Stéphane Graber ]
* Fix lxc-ubuntu and lxc-ubuntu-cloud to fix the /dev/shm workaround to only
trigger when /dev/shm is not a symlink. (LP: #974584)
[ Serge
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu21
---
lxc (0.8.0~rc1-4ubuntu21) quantal; urgency=low
[ Stéphane Graber ]
* Fix lxc-ubuntu and lxc-ubuntu-cloud to fix the /dev/shm workaround to only
trigger when /dev/shm is not a symlink. (LP: #974584)
[ Serge
I took a look at this last night and wrote a patch, which seems to work
on my test cluster.
http://article.gmane.org/gmane.comp.file-systems.ceph.devel/8170
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
Public bug reported:
Occured while trying to purge all installed lxc packages.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: lxc (not installed)
ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
Uname: Linux 3.2.0-27-generic x86_64
ApportVersion: 2.0.1-0ubuntu11
Architecture:
--
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/1029716
Title:
package lxc (not installed) failed to install/upgrade: subprocess
installed post-removal script returned error exit
This bug was fixed in the package maas - 0.1+bzr777+dfsg-0ubuntu1
---
maas (0.1+bzr777+dfsg-0ubuntu1) quantal-proposed; urgency=low
* New upstream release
* Only run 'maas' command as root. (LP: #974046)
- debian/extras/maas: Check id.
- debian/maas.install: Install in
** Also affects: cloud-init
Importance: Undecided
Status: New
--
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/1028674
Title:
Quantal Alpha-3 cloud images tested as
** Branch linked: lp: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/1028674
Title:
Quantal Alpha-3 cloud images tested as unstable for multi-part-ud
To manage
fixed in trunk revno 610
** Changed in: cloud-init
Status: New = Fix Committed
** Changed in: cloud-init
Assignee: (unassigned) = Scott Moser (smoser)
** Changed in: cloud-init
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
** Changed in: lxc (Ubuntu)
Status: New = Triaged
** Changed in: lxc (Ubuntu)
Importance: Undecided = Critical
** Changed in: lxc (Ubuntu)
Importance: Critical = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc
Thanks for submitting this bug, the postrm script does indeed have a bug
which is present in precise but not quantal. Ill therefore mark this
fix released and request SRU for the postrm fix for precise.
** Also affects: lxc (Ubuntu Precise)
Importance: Undecided
Status: New
** Also
** Patch added: Debdiff fixing this bug.
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1029716/+attachment/3237980/+files/lxc-purge.debdiff
** Description changed:
+ =
+ SRU Justification:
+ 1. Impact: 'apt-get purge lxc' fails
+ 2. Development fix:
Evgeny, you can use netstat -tnp |grep curl to get the other port
number of the connection from curl to apache2. With that, you can look
for the other end of the connection in netstat -tnp output. The last
column should give be 123/apache2 where 123 is the pid of the apache2
process. You will
Public bug reported:
/etc/cron.daily/logrotate:
keystone start/running, process 3663
Need to pipe the restart keystone command to dev null
If someone could show me how to provide a patch I can do this. I usually
do it all through gerrit but never done a patch to the specific package
before
**
Package is built now.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1023550
Title:
Postfix missing libresolv in chroot jail
To manage notifications about this bug go to:
72 matches
Mail list logo
